From lmohanty at redhat.com Mon Jul 4 14:05:01 2016 From: lmohanty at redhat.com (Lalatendu Mohanty) Date: Mon, 4 Jul 2016 19:35:01 +0530 Subject: [Devtools] Atomic Developer Bundle videos available in Youtube Message-ID: <98448c6b-4a8b-47d0-d288-e60fe2c671ef@redhat.com> We have 4 videos till now and they are available in Project Atomic Youtube channel [1]. Here are the details. Mesos Marathon set up: https://www.youtube.com/watch?v=8x-aU_jD3nw OpenShift set up: https://www.youtube.com/watch?v=HiE7TgjLjAk Kubernetes set up: https://www.youtube.com/watch?v=zZJntrcp4UQ Native Docker experience : https://www.youtube.com/watch?v=UJYosiwHhxc [1] https://www.youtube.com/channel/UCDFLt2fl262b9n0tSW_4vyQ Thanks, Lala From cdrage at redhat.com Mon Jul 4 18:20:39 2016 From: cdrage at redhat.com (Charlie Drage) Date: Mon, 4 Jul 2016 14:20:39 -0400 Subject: [Devtools] Creation of projectatomic/nulecule-library Docker Hub file Message-ID: <20160704182039.GA1@7177a189328f> Hey all, With the work I've been doing on the `atomicapp index` PR (well, picking up on the work that vpavlin did), I require the creation of a new Docker image that will contain the `index.yaml` file on hub.docker.com/projectatomic I have permission for the files, however, I want people's input before I add it. Should the name be `projectatomic/index` or `projectatomic/nulecule-library-index` or something of the rather? PR source: https://github.com/projectatomic/atomicapp/pull/750 -- Charlie Drage Red Hat - OSAS Team / Project Atomic 4096R / 0x9B3B446C http://pgp.mit.edu/pks/lookup?op=get&search=0x622CDF119B3B446C From jstracha at redhat.com Tue Jul 5 08:34:32 2016 From: jstracha at redhat.com (James Strachan) Date: Tue, 5 Jul 2016 09:34:32 +0100 Subject: [Devtools] support for OpenShift Container Platform / Origin in minikube? Message-ID: <34C29FC6-B5F2-439B-95F4-2D42A156E35E@redhat.com> Minikube is looking like a great option for folks trying out Kubernetes on their laptops (Linux / Mac / Windows) and will shortly have native support for xhyve / hyperv to avoid the Vagrant / VirtualBox stuff if using a mac / windows box. i.e. giving a native feel like Docker for Mac / Windows all from a single binary for each platform. https://github.com/kubernetes/minikube It might be nice to look at how easy it?d be to get OpenShift Container Platform & Origin to work with minikube as a leaner, meaner, more native equivalent of the CDK? Minikube already supports pluggable ISOs via `minikube start --iso-url ?' so hopefully won?t be too hard? James ------- Red Hat Twitter: @jstrachan Email: jstracha at redhat.com Blog: https://medium.com/@jstrachan/ fabric8: http://fabric8.io/ open source microservices platform -------------- next part -------------- An HTML attachment was scrubbed... URL: From jstracha at redhat.com Tue Jul 5 08:56:53 2016 From: jstracha at redhat.com (James Strachan) Date: Tue, 5 Jul 2016 09:56:53 +0100 Subject: [Devtools] support for OpenShift Container Platform / Origin in minikube? In-Reply-To: <34C29FC6-B5F2-439B-95F4-2D42A156E35E@redhat.com> References: <34C29FC6-B5F2-439B-95F4-2D42A156E35E@redhat.com> Message-ID: > On 5 Jul 2016, at 09:34, James Strachan wrote: > > Minikube is looking like a great option for folks trying out Kubernetes on their laptops (Linux / Mac / Windows) and will shortly have native support for xhyve / hyperv to avoid the Vagrant / VirtualBox stuff if using a mac / windows box. i.e. giving a native feel like Docker for Mac / Windows all from a single binary for each platform. > https://github.com/kubernetes/minikube > > It might be nice to look at how easy it?d be to get OpenShift Container Platform & Origin to work with minikube as a leaner, meaner, more native equivalent of the CDK? Minikube already supports pluggable ISOs via `minikube start --iso-url ?' so hopefully won?t be too hard? Jimmi suggested just copying the binaries into the linux VM might do the trick; so could be even easier to support OCP / Origin in minikube. James ------- Red Hat Twitter: @jstrachan Email: jstracha at redhat.com Blog: https://medium.com/@jstrachan/ fabric8: http://fabric8.io/ open source microservices platform -------------- next part -------------- An HTML attachment was scrubbed... URL: From cdrage at redhat.com Tue Jul 5 12:02:57 2016 From: cdrage at redhat.com (Charlie Drage) Date: Tue, 5 Jul 2016 08:02:57 -0400 Subject: [Devtools] Atomic App 0.6.1 Release Message-ID: <20160705120257.GA1@9695504d5843> Hey all! We'll be releasing 0.6.1 of Atomic App tomorrow in the late afternoon (1600-1700 EST). Ping the respective people if you still want your PR merged in before the release :) -- Charlie Drage Red Hat - OSAS Team / Project Atomic 4096R / 0x9B3B446C http://pgp.mit.edu/pks/lookup?op=get&search=0x622CDF119B3B446C From rwagner at redhat.com Tue Jul 5 15:07:10 2016 From: rwagner at redhat.com (Rick Wagner) Date: Tue, 5 Jul 2016 10:07:10 -0500 Subject: [Devtools] Thanks for the videos! Message-ID: Great thanks to Fred, Praveen and anyone else publishing videos on YouTube for Dev Tools. These are a great help. Here's a quick top 5 reasons these videos rock: 5. You get to see the user's gestures in the IDE/environment, you learn much faster than trying to follow written doc. 4. It's often easier to watch/hear technical content than read technical content. 3. No need for screen shots in doc, which seems to map to mental context switches. Videos just flow. 2. It's a great way to teach the learner how to do something. ('Pause' is valuable here.) Great for times when you're doing something wrong, but don't know what it is. 1. Videos often have sound, which lets you listen to what the SME is thinking. This extra context (not found in written doc) lets you gain insights that are otherwise unavailable. Thank you, thank you, thank you. Rick -------------- next part -------------- An HTML attachment was scrubbed... URL: From bsutter at redhat.com Tue Jul 5 17:07:20 2016 From: bsutter at redhat.com (Burr Sutter) Date: Tue, 5 Jul 2016 13:07:20 -0400 Subject: [Devtools] support for OpenShift Container Platform / Origin in minikube? In-Reply-To: References: <34C29FC6-B5F2-439B-95F4-2D42A156E35E@redhat.com> Message-ID: This is something that needs to be considered as installation/configuration of the CDK currently requires a very skillful and dedicated user On Tuesday, July 5, 2016, James Strachan wrote: > > On 5 Jul 2016, at 09:34, James Strachan > wrote: > > Minikube is looking like a great option for folks trying out Kubernetes on > their laptops (Linux / Mac / Windows) and will shortly have native support > for xhyve / hyperv to avoid the Vagrant / VirtualBox stuff if using a mac / > windows box. i.e. giving a native feel like Docker for Mac / Windows all > from a single binary for each platform. > https://github.com/kubernetes/minikube > > It might be nice to look at how easy it?d be to get OpenShift Container > Platform & Origin to work with minikube as a leaner, meaner, more native > equivalent of the CDK? Minikube already supports pluggable ISOs via > `minikube start --iso-url ?' so hopefully won?t be too hard? > > > Jimmi suggested just copying the binaries into the linux VM might do the > trick; so could be even easier to support OCP / Origin in minikube. > > James > ------- > Red Hat > > Twitter: @jstrachan > Email: jstracha at redhat.com > > Blog: https://medium.com/@jstrachan/ > > fabric8: http://fabric8.io/ > open source microservices platform > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From jstracha at redhat.com Tue Jul 5 17:09:41 2016 From: jstracha at redhat.com (James Strachan) Date: Tue, 5 Jul 2016 18:09:41 +0100 Subject: [Devtools] support for OpenShift Container Platform / Origin in minikube? In-Reply-To: References: <34C29FC6-B5F2-439B-95F4-2D42A156E35E@redhat.com> Message-ID: <217D53D0-D256-48E5-8D26-CFD36BF44AC7@redhat.com> Agreed. Once the xhyve, hyperv and kvm drivers are embedded into the single minikube binary, its gonna be super simple to use! Just one binary; nothing else required to be installed on the OS X / Windows / Linux box! > On 5 Jul 2016, at 18:07, Burr Sutter wrote: > > This is something that needs to be considered as installation/configuration of the CDK currently requires a very skillful and dedicated user > > On Tuesday, July 5, 2016, James Strachan > wrote: > >> On 5 Jul 2016, at 09:34, James Strachan > wrote: >> >> Minikube is looking like a great option for folks trying out Kubernetes on their laptops (Linux / Mac / Windows) and will shortly have native support for xhyve / hyperv to avoid the Vagrant / VirtualBox stuff if using a mac / windows box. i.e. giving a native feel like Docker for Mac / Windows all from a single binary for each platform. >> https://github.com/kubernetes/minikube >> >> It might be nice to look at how easy it?d be to get OpenShift Container Platform & Origin to work with minikube as a leaner, meaner, more native equivalent of the CDK? Minikube already supports pluggable ISOs via `minikube start --iso-url ?' so hopefully won?t be too hard? > > Jimmi suggested just copying the binaries into the linux VM might do the trick; so could be even easier to support OCP / Origin in minikube. > > James > ------- > Red Hat > > Twitter: @jstrachan > Email: jstracha at redhat.com > Blog: https://medium.com/@jstrachan/ > > fabric8: http://fabric8.io/ > open source microservices platform > James ------- Red Hat Twitter: @jstrachan Email: jstracha at redhat.com Blog: https://medium.com/@jstrachan/ fabric8: http://fabric8.io/ open source microservices platform -------------- next part -------------- An HTML attachment was scrubbed... URL: From manderse at redhat.com Tue Jul 5 22:53:03 2016 From: manderse at redhat.com (Max Rydahl Andersen) Date: Wed, 06 Jul 2016 00:53:03 +0200 Subject: [Devtools] support for OpenShift Container Platform / Origin in minikube? In-Reply-To: <217D53D0-D256-48E5-8D26-CFD36BF44AC7@redhat.com> References: <34C29FC6-B5F2-439B-95F4-2D42A156E35E@redhat.com> <217D53D0-D256-48E5-8D26-CFD36BF44AC7@redhat.com> Message-ID: looks great. would this be able to run red hat's variation of docker ? and how about openshift itself ? /max > Agreed. Once the xhyve, hyperv and kvm drivers are embedded into the > single minikube binary, its gonna be super simple to use! Just one > binary; nothing else required to be installed on the OS X / Windows / > Linux box! > >> On 5 Jul 2016, at 18:07, Burr Sutter wrote: >> >> This is something that needs to be considered as >> installation/configuration of the CDK currently requires a very >> skillful and dedicated user >> >> On Tuesday, July 5, 2016, James Strachan > > wrote: >> >>> On 5 Jul 2016, at 09:34, James Strachan >> > wrote: >>> >>> Minikube is looking like a great option for folks trying out >>> Kubernetes on their laptops (Linux / Mac / Windows) and will shortly >>> have native support for xhyve / hyperv to avoid the Vagrant / >>> VirtualBox stuff if using a mac / windows box. i.e. giving a native >>> feel like Docker for Mac / Windows all from a single binary for each >>> platform. >>> https://github.com/kubernetes/minikube >>> >>> >>> It might be nice to look at how easy it?d be to get OpenShift >>> Container Platform & Origin to work with minikube as a leaner, >>> meaner, more native equivalent of the CDK? Minikube already supports >>> pluggable ISOs via `minikube start --iso-url ?' so hopefully >>> won?t be too hard? >> >> Jimmi suggested just copying the binaries into the linux VM might do >> the trick; so could be even easier to support OCP / Origin in >> minikube. >> >> James >> ------- >> Red Hat >> >> Twitter: @jstrachan >> Email: jstracha at redhat.com >> >> Blog: https://medium.com/@jstrachan/ >> >> fabric8: http://fabric8.io/ >> open source microservices platform >> > > James > ------- > Red Hat > > Twitter: @jstrachan > Email: jstracha at redhat.com > Blog: https://medium.com/@jstrachan/ > > fabric8: http://fabric8.io/ > open source microservices platform > _______________________________________________ > Devtools mailing list > Devtools at redhat.com > https://www.redhat.com/mailman/listinfo/devtools /max http://about.me/maxandersen -------------- next part -------------- An HTML attachment was scrubbed... URL: From jstracha at redhat.com Wed Jul 6 06:57:57 2016 From: jstracha at redhat.com (James Strachan) Date: Wed, 6 Jul 2016 07:57:57 +0100 Subject: [Devtools] support for OpenShift Container Platform / Origin in minikube? In-Reply-To: References: <34C29FC6-B5F2-439B-95F4-2D42A156E35E@redhat.com> <217D53D0-D256-48E5-8D26-CFD36BF44AC7@redhat.com> Message-ID: <694CB8BF-DEC6-4EF8-891C-B16DB1F5F93F@redhat.com> We could fork minikube; use it for all the developer UX and virtualisation and just switch the VM thats used internally to RHEL for OSCP. As Jimmi said, for OSCP / OSO we could just use the binaries directly in the VM > On 5 Jul 2016, at 23:53, Max Rydahl Andersen wrote: > > looks great. would this be able to run red hat's variation of docker ? and how about openshift itself ? > > /max > > Agreed. Once the xhyve, hyperv and kvm drivers are embedded into the single minikube binary, its gonna be super simple to use! Just one binary; nothing else required to be installed on the OS X / Windows / Linux box! > >> On 5 Jul 2016, at 18:07, Burr Sutter > wrote: >> >> This is something that needs to be considered as installation/configuration of the CDK currently requires a very skillful and dedicated user >> >> On Tuesday, July 5, 2016, James Strachan > wrote: >> >>> On 5 Jul 2016, at 09:34, James Strachan > wrote: >>> >>> Minikube is looking like a great option for folks trying out Kubernetes on their laptops (Linux / Mac / Windows) and will shortly have native support for xhyve / hyperv to avoid the Vagrant / VirtualBox stuff if using a mac / windows box. i.e. giving a native feel like Docker for Mac / Windows all from a single binary for each platform. >>> https://github.com/kubernetes/minikube >>> >>> It might be nice to look at how easy it?d be to get OpenShift Container Platform & Origin to work with minikube as a leaner, meaner, more native equivalent of the CDK? Minikube already supports pluggable ISOs via `minikube start --iso-url ?' so hopefully won?t be too hard? >> >> Jimmi suggested just copying the binaries into the linux VM might do the trick; so could be even easier to support OCP / Origin in minikube. >> >> James >> ------- >> Red Hat >> >> Twitter: @jstrachan >> Email: jstracha at redhat.com >> Blog: https://medium.com/@jstrachan/ >> >> fabric8: http://fabric8.io/ >> open source microservices platform >> > > > James > ------- > Red Hat > > Twitter: @jstrachan > Email: jstracha at redhat.com > Blog: https://medium.com/@jstrachan/ > > fabric8: http://fabric8.io/ > open source microservices platform > > > _______________________________________________ > Devtools mailing list > Devtools at redhat.com > https://www.redhat.com/mailman/listinfo/devtools > > > /max > http://about.me/maxandersen James ------- Red Hat Twitter: @jstrachan Email: jstracha at redhat.com Blog: https://medium.com/@jstrachan/ fabric8: http://fabric8.io/ open source microservices platform -------------- next part -------------- An HTML attachment was scrubbed... URL: From hferents at redhat.com Wed Jul 6 07:32:24 2016 From: hferents at redhat.com (Hardy Ferentschik) Date: Wed, 6 Jul 2016 09:32:24 +0200 Subject: [Devtools] support for OpenShift Container Platform / Origin in minikube? In-Reply-To: References: <34C29FC6-B5F2-439B-95F4-2D42A156E35E@redhat.com> <217D53D0-D256-48E5-8D26-CFD36BF44AC7@redhat.com> Message-ID: <20160706073224.GE96345@nineveh.lan> On Wed, 06-Jul-2016 00:53, Max Rydahl Andersen wrote: > looks great. would this be able to run red hat's variation of docker ? and > how about openshift itself ? My thinking as well. Might be worth investigating. A miniopenshift would have a great appeal. --Hardy -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 496 bytes Desc: not available URL: From rwagner at redhat.com Wed Jul 6 15:08:09 2016 From: rwagner at redhat.com (Rick Wagner) Date: Wed, 6 Jul 2016 10:08:09 -0500 Subject: [Devtools] Development Suite installation question - C/O SME with knowledge of installer edits Message-ID: Hello DevTools, We have a customer case that deals with the error message "Terms and Conditions for the CDK have not been signed". (Actually, this is the second case in 2 days for this problem.) The customer has tried the suggested workaround, without satisfactory results. ("This error appears on the *Log In* page when starting the Installer. To fix the problem, start downloading the Installer to ensure the *Terms and Conditions* are viewed and accepted and then cancel the binary download." We offer this suggestion in the knowledge article at [1].) Can a knowledgeable SME please offer ideas about alternative courses of action? Extra credit: Can you please point me to the source code that produces this edit error? A little spelunking by the Support team sometimes helps with related issues. Thanks! Rick [1] https://access.redhat.com/articles/2360571 -------------- next part -------------- An HTML attachment was scrubbed... URL: From alkazako at redhat.com Wed Jul 6 15:32:43 2016 From: alkazako at redhat.com (Alexey Kazakov) Date: Wed, 6 Jul 2016 11:32:43 -0400 Subject: [Devtools] Development Suite installation question - C/O SME with knowledge of installer edits In-Reply-To: References: Message-ID: <577D249B.1000802@redhat.com> On 07/06/2016 11:08 AM, Rick Wagner wrote: > Hello DevTools, > > We have a customer case that deals with the error message "Terms and > Conditions for the CDK have not been signed". (Actually, this is the > second case in 2 days for this problem.) > > The customer has tried the suggested workaround, without satisfactory > results. ("This error appears on the *Log In* page when starting the > Installer. To fix the problem, start downloading the Installer to > ensure the /Terms and Conditions/ are viewed and accepted and then > cancel the binary download." We offer this suggestion in the > knowledge article at [1].) > > Can a knowledgeable SME please offer ideas about alternative courses > of action? > > Extra credit: Can you please point me to the source code that > produces this edit error? A little spelunking by the Support team > sometimes helps with related issues. See https://github.com/redhat-developer-tooling/developer-platform-install/blob/0db7dbb96be2716e7f8e5a0eaa3fb353382fa528/browser/pages/account/controller.js#L32-L46 and https://github.com/redhat-developer-tooling/developer-platform-install/blob/0db7dbb96be2716e7f8e5a0eaa3fb353382fa528/browser/pages/account/account.html#L31-L34 > > Thanks! > > Rick > > [1] https://access.redhat.com/articles/2360571 > > > _______________________________________________ > Devtools mailing list > Devtools at redhat.com > https://www.redhat.com/mailman/listinfo/devtools -------------- next part -------------- An HTML attachment was scrubbed... URL: From rkratky at redhat.com Wed Jul 6 15:51:03 2016 From: rkratky at redhat.com (Robert Kratky) Date: Wed, 06 Jul 2016 17:51:03 +0200 Subject: [Devtools] Development Suite installation question - C/O SME with knowledge of installer edits In-Reply-To: References: Message-ID: <4892002.EmcPcHGPPG@x230> On 6.?7.?2016 10:08:09, Rick Wagner wrote: > Hello DevTools, > > We have a customer case that deals with the error message "Terms and > Conditions for the CDK have not been signed". (Actually, this is the > second case in 2 days for this problem.) > > The customer has tried the suggested workaround, without satisfactory > results. ("This error appears on the *Log In* page when starting the > Installer. To fix the problem, start downloading the Installer to ensure > the *Terms and Conditions* are viewed and accepted and then cancel the > binary download." We offer this suggestion in the knowledge article at > [1].) > > Can a knowledgeable SME please offer ideas about alternative courses of > action? Hi Rick, The problem happens quite often, apparently. I asked about this last Friday in devtools-program [a] -- on behalf of a user who reported the problem in a comment under the old version of the Kbase article [b]. Any workaround would be appreciated. Thanks. Robert [a] http://post-office.corp.redhat.com/archives/devtools-program/2016-July/msg00001.html [b] https://access.redhat.com/articles/2255391#comment-1066361 > Extra credit: Can you please point me to the source code that produces > this edit error? A little spelunking by the Support team sometimes helps > with related issues. > > Thanks! > > Rick > > [1] https://access.redhat.com/articles/2360571 From dusty at dustymabe.com Wed Jul 6 18:56:39 2016 From: dusty at dustymabe.com (Dusty Mabe) Date: Wed, 6 Jul 2016 14:56:39 -0400 Subject: [Devtools] Creation of projectatomic/nulecule-library Docker Hub file In-Reply-To: <20160704182039.GA1@7177a189328f> References: <20160704182039.GA1@7177a189328f> Message-ID: <577D5467.6030306@dustymabe.com> On 07/04/2016 02:20 PM, Charlie Drage wrote: > Hey all, > > With the work I've been doing on the `atomicapp index` PR (well, > picking up on the work that vpavlin did), I require the creation of a > new Docker image that will contain the `index.yaml` file on > hub.docker.com/projectatomic > > I have permission for the files, however, I want people's input before > I add it. > > Should the name be `projectatomic/index` or > `projectatomic/nulecule-library-index` or something of the rather? > > PR source: https://github.com/projectatomic/atomicapp/pull/750 > Dumb question - do we need this in a container or could it just be a yaml file that is hosted somewhere (http/https). If someone wanted to override the location of the index we could easily support that as well. Dusty From rwagner at redhat.com Wed Jul 6 19:02:27 2016 From: rwagner at redhat.com (Rick Wagner) Date: Wed, 6 Jul 2016 14:02:27 -0500 Subject: [Devtools] Fix an installer problem with a server-side change? Message-ID: Hello DevTools, It seems we have a problem with the current version of the Development Suite installer. We have at least 2 new customer cases reporting inability to install due to the message dialogue "Terms and Conditions for the CDK have not been signed". This is concerning because we're also seeing similar activity on non-support channels. It's also worth noting that not every user that has a problem reports it-- some just give up and move on. There is enough volume here that we probably should treat this with some urgency. It seems likely the relevant code (thanks for highlighting this, Alexey) is below: ------------------------------------------------- login() { this.authFailed = false; this.tandcNotSigned = false; let req = { method: 'GET', url: 'https://developers.redhat.com/download-manager/rest/tc-accepted?downloadURL=/file/cdk-2.0.0-beta3.zip', <<<<<<<<<---- returns 'false' when not approved headers: { 'Authorization': 'Basic ' + this.base64.encode(this.username + ':' + this.password) } }; this.http(req) .then(this.handleHttpSuccess.bind(this)) .catch(this.handleHttpFailure.bind(this)); } --------------------------------- So we have users getting denied use of our product. Do we require a rebuild immediately? Maybe. How about if we changed the rest service (https://developers.redhat.com/download-manager/rest/tc-accepted) so it includes a peak at an override database as well as whatever it's currently doing now? In that way, we could have the users pop over to a 'yes, I agree to the terms' page to insert an entry into the database. The rest service could use something like the provided username as a key to ensure a 'true' is returned. Or not. Is there a better way to fix this? Please consider, we need to fix this sooner rather than later.... Thanks, Rick -------------- next part -------------- An HTML attachment was scrubbed... URL: From cdrage at redhat.com Wed Jul 6 19:02:46 2016 From: cdrage at redhat.com (Charlie Drage) Date: Wed, 6 Jul 2016 15:02:46 -0400 Subject: [Devtools] Creation of projectatomic/nulecule-library Docker Hub file In-Reply-To: <577D5467.6030306@dustymabe.com> References: <20160704182039.GA1@7177a189328f> <577D5467.6030306@dustymabe.com> Message-ID: <20160706190246.GB1@1f9b86abf2d2> Yeah, I'm only doing it via container since instead of relying of us hosting the yaml file, we can rely on the docker hub instead. Gives us easy access to update it, etc. Just going by how vpavlin implemented it too :) On 07/06, Dusty Mabe wrote: > > > On 07/04/2016 02:20 PM, Charlie Drage wrote: > > Hey all, > > > > With the work I've been doing on the `atomicapp index` PR (well, > > picking up on the work that vpavlin did), I require the creation of a > > new Docker image that will contain the `index.yaml` file on > > hub.docker.com/projectatomic > > > > I have permission for the files, however, I want people's input before > > I add it. > > > > Should the name be `projectatomic/index` or > > `projectatomic/nulecule-library-index` or something of the rather? > > > > PR source: https://github.com/projectatomic/atomicapp/pull/750 > > > > Dumb question - do we need this in a container or could it just be a yaml > file that is hosted somewhere (http/https). > > If someone wanted to override the location of the index we could easily > support that as well. > > Dusty > > _______________________________________________ > Devtools mailing list > Devtools at redhat.com > https://www.redhat.com/mailman/listinfo/devtools -- Charlie Drage Red Hat - Dev Tools / Project Atomic PGP - 4096R/C037D617 http://pgp.mit.edu/pks/lookup?op=get&search=0xDA227403C037D617 From degolovi at redhat.com Wed Jul 6 19:38:04 2016 From: degolovi at redhat.com (Denis Golovin) Date: Wed, 6 Jul 2016 15:38:04 -0400 (EDT) Subject: [Devtools] Development Suite installation question - C/O SME with knowledge of installer edits In-Reply-To: <4892002.EmcPcHGPPG@x230> References: <4892002.EmcPcHGPPG@x230> Message-ID: <573810996.3897959.1467833884253.JavaMail.zimbra@redhat.com> T&C's signing workflow is not user friendly ATM. Workaround mentioned in https://access.redhat.com/articles/2360571 worked before for many dev's who was testing installer. I am going to do check full T&C's signing again today and send update ASAP. This problem should be affecting only customers who didn't get installer directly from develper.redhat.com download. Denis ----- Original Message ----- > From: "Robert Kratky" > To: devtools at redhat.com > Cc: "Rick Wagner" > Sent: Wednesday, July 6, 2016 8:51:03 AM > Subject: Re: [Devtools] Development Suite installation question - C/O SME with knowledge of installer edits > > On 6.?7.?2016 10:08:09, Rick Wagner wrote: > > > Hello DevTools, > > > > We have a customer case that deals with the error message "Terms and > > Conditions for the CDK have not been signed". (Actually, this is the > > second case in 2 days for this problem.) > > > > The customer has tried the suggested workaround, without satisfactory > > results. ("This error appears on the *Log In* page when starting the > > Installer. To fix the problem, start downloading the Installer to ensure > > the *Terms and Conditions* are viewed and accepted and then cancel the > > binary download." We offer this suggestion in the knowledge article at > > [1].) > > > > Can a knowledgeable SME please offer ideas about alternative courses of > > action? > > Hi Rick, > > The problem happens quite often, apparently. I asked about this last Friday > in devtools-program [a] -- on behalf of a user who reported the problem in a > comment under the old version of the Kbase article [b]. > > Any workaround would be appreciated. > > Thanks. > > Robert > > [a] > http://post-office.corp.redhat.com/archives/devtools-program/2016-July/msg00001.html > [b] https://access.redhat.com/articles/2255391#comment-1066361 > > > Extra credit: Can you please point me to the source code that produces > > this edit error? A little spelunking by the Support team sometimes helps > > with related issues. > > > > Thanks! > > > > Rick > > > > [1] https://access.redhat.com/articles/2360571 > > > _______________________________________________ > Devtools mailing list > Devtools at redhat.com > https://www.redhat.com/mailman/listinfo/devtools > From alkazako at redhat.com Wed Jul 6 19:45:01 2016 From: alkazako at redhat.com (Alexey Kazakov) Date: Wed, 6 Jul 2016 15:45:01 -0400 Subject: [Devtools] Fix an installer problem with a server-side change? In-Reply-To: References: Message-ID: <577D5FBD.30209@redhat.com> BTW do we have a jira for that problem? On 07/06/2016 03:02 PM, Rick Wagner wrote: > Hello DevTools, > > It seems we have a problem with the current version of the Development > Suite installer. We have at least 2 new customer cases reporting > inability to install due to the message dialogue "Terms and Conditions > for the CDK have not been signed". > > This is concerning because we're also seeing similar activity on > non-support channels. It's also worth noting that not every user that > has a problem reports it-- some just give up and move on. There is > enough volume here that we probably should treat this with some urgency. > > It seems likely the relevant code (thanks for highlighting this, > Alexey) is below: > > ------------------------------------------------- > login() { > this.authFailed = false; > this.tandcNotSigned = false; > > let req = { > method: 'GET', > url: 'https://developers.redhat.com/download-manager/rest/tc-accepted?downloadURL=/file/cdk-2.0.0-beta3.zip', <<<<<<<<<---- returns 'false' when not approved > headers: { > 'Authorization': 'Basic ' + this.base64.encode(this.username + ':' + this.password) > } > }; > > this.http(req) > .then(this.handleHttpSuccess.bind(this)) > .catch(this.handleHttpFailure.bind(this)); > } > > --------------------------------- > > > So we have users getting denied use of our product. Do we require a rebuild immediately? Maybe. > > How about if we changed the rest service (https://developers.redhat.com/download-manager/rest/tc-accepted) so it includes a peak at an override database as well as whatever it's currently doing now? > In that way, we could have the users pop over to a 'yes, I agree to the terms' page to insert an entry into the database. The rest service could use something like the provided username as a key to ensure a 'true' is returned. > > > Or not. Is there a better way to fix this? > > Please consider, we need to fix this sooner rather than later.... > > Thanks, > > Rick > > > _______________________________________________ > 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 Wed Jul 6 20:11:23 2016 From: degolovi at redhat.com (Denis Golovin) Date: Wed, 6 Jul 2016 16:11:23 -0400 (EDT) Subject: [Devtools] Fix an installer problem with a server-side change? In-Reply-To: References: Message-ID: <2069914337.3902671.1467835883831.JavaMail.zimbra@redhat.com> Rick, This should be the case for those who hasn't downloaded devsuite directly from developer.redhat.com. Workaround mentioned in documentation should work and I walking throw this workflow from scratch to verify nothing is changed since I did it last time right before summit. Simple test is curl https://username%40mailserver.com:password at developers.redhat.com/download-manager/rest/tc-accepted?downloadURL=/file/cdk-2.0.0-beta3.zip works for users previously signed T&C's before download from develoers.redhat.com. Just changing rest would not work as I understand, because additional information in profile is required before developer with developer.redhat.com account can proceed with T&C's signing. Denis ----- Original Message ----- > From: "Rick Wagner" > To: devtools at redhat.com > Sent: Wednesday, July 6, 2016 12:02:27 PM > Subject: [Devtools] Fix an installer problem with a server-side change? > > Hello DevTools, > > It seems we have a problem with the current version of the Development Suite > installer. We have at least 2 new customer cases reporting inability to > install due to the message dialogue "Terms and Conditions for the CDK have > not been signed". > > This is concerning because we're also seeing similar activity on non-support > channels. It's also worth noting that not every user that has a problem > reports it-- some just give up and move on. There is enough volume here that > we probably should treat this with some urgency. > > It seems likely the relevant code (thanks for highlighting this, Alexey) is > below: > > ------------------------------------------------- > login() { > this.authFailed = false; > this.tandcNotSigned = false; > > let req = { > method: 'GET', > url: ' > https://developers.redhat.com/download-manager/rest/tc-accepted?downloadURL=/file/cdk-2.0.0-beta3.zip > ', <<<<<<<<<---- returns 'false' when not approved > headers: { > 'Authorization': 'Basic ' + this.base64.encode(this.username + ':' + > this.password) > } > }; > > this.http(req) > .then(this.handleHttpSuccess.bind(this)) > .catch(this.handleHttpFailure.bind(this)); > } > > --------------------------------- > > > So we have users getting denied use of our product. Do we require a rebuild > immediately? Maybe. > > How about if we changed the rest service ( > https://developers.redhat.com/download-manager/rest/tc-accepted ) so it > includes a peak at an override database as well as whatever it's currently > doing now? > In that way, we could have the users pop over to a 'yes, I agree to the > terms' page to insert an entry into the database. The rest service could > use something like the provided username as a key to ensure a 'true' is > returned. > > > Or not. Is there a better way to fix this? > > Please consider, we need to fix this sooner rather than later.... > > Thanks, > > Rick > > _______________________________________________ > Devtools mailing list > Devtools at redhat.com > https://www.redhat.com/mailman/listinfo/devtools > From degolovi at redhat.com Wed Jul 6 20:13:07 2016 From: degolovi at redhat.com (Denis Golovin) Date: Wed, 6 Jul 2016 16:13:07 -0400 (EDT) Subject: [Devtools] Fix an installer problem with a server-side change? In-Reply-To: <577D5FBD.30209@redhat.com> References: <577D5FBD.30209@redhat.com> Message-ID: <1468060034.3902902.1467835987347.JavaMail.zimbra@redhat.com> https://issues.jboss.org/browse/JBDS-3627 would be the original issue. ----- Original Message ----- > From: "Alexey Kazakov" > To: devtools at redhat.com > Sent: Wednesday, July 6, 2016 12:45:01 PM > Subject: Re: [Devtools] Fix an installer problem with a server-side change? > > BTW do we have a jira for that problem? > > On 07/06/2016 03:02 PM, Rick Wagner wrote: > > > > Hello DevTools, > > It seems we have a problem with the current version of the Development Suite > installer. We have at least 2 new customer cases reporting inability to > install due to the message dialogue "Terms and Conditions for the CDK have > not been signed". > > This is concerning because we're also seeing similar activity on non-support > channels. It's also worth noting that not every user that has a problem > reports it-- some just give up and move on. There is enough volume here that > we probably should treat this with some urgency. > > It seems likely the relevant code (thanks for highlighting this, Alexey) is > below: > > ------------------------------------------------- > login() { > this.authFailed = false; > this.tandcNotSigned = false; > > let req = { > method: 'GET', > url: ' > https://developers.redhat.com/download-manager/rest/tc-accepted?downloadURL=/file/cdk-2.0.0-beta3.zip > ', <<<<<<<<<---- returns 'false' when not approved > headers: { > 'Authorization': 'Basic ' + this.base64.encode(this.username + ':' + > this.password) > } > }; > > this.http(req) > .then(this.handleHttpSuccess.bind(this)) > .catch(this.handleHttpFailure.bind(this)); > } > > --------------------------------- > So we have users getting denied use of our product. Do we require a rebuild > immediately? Maybe. > How about if we changed the rest service ( > https://developers.redhat.com/download-manager/rest/tc-accepted ) so it > includes a peak at an override database as well as whatever it's currently > doing now? > In that way, we could have the users pop over to a 'yes, I agree to the > terms' page to insert an entry into the database. The rest service could > use something like the provided username as a key to ensure a 'true' is > returned. > Or not. Is there a better way to fix this? > Please consider, we need to fix this sooner rather than later.... > Thanks, > Rick > > > _______________________________________________ > 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 > From rwagner at redhat.com Wed Jul 6 21:01:51 2016 From: rwagner at redhat.com (Rick Wagner) Date: Wed, 6 Jul 2016 16:01:51 -0500 Subject: [Devtools] Fix an installer problem with a server-side change? Message-ID: Hi Alexey, Yes, there is a JIRA already [1]. Thanks, Rick [1] https://issues.jboss.org/browse/JBDS-3627 ------------------------------ Message: 5 Date: Wed, 6 Jul 2016 15:45:01 -0400 From: Alexey Kazakov To: devtools at redhat.com Subject: Re: [Devtools] Fix an installer problem with a server-side change? Message-ID: <577D5FBD.30209 at redhat.com> Content-Type: text/plain; charset="windows-1252"; Format="flowed" BTW do we have a jira for that problem? -------------- next part -------------- An HTML attachment was scrubbed... URL: From rwagner at redhat.com Wed Jul 6 21:03:49 2016 From: rwagner at redhat.com (Rick Wagner) Date: Wed, 6 Jul 2016 16:03:49 -0500 Subject: [Devtools] Fix an installer problem with a server-side change? Message-ID: Hi Denis, Thanks much for that idea. I've written our customers, let's see if they can coax a 'true' out of curl. That may help us get to the bottom of the problem, let's see. Rick ------------------------------ Message: 6 Date: Wed, 6 Jul 2016 16:11:23 -0400 (EDT) From: Denis Golovin To: Rick Wagner Cc: devtools at redhat.com Subject: Re: [Devtools] Fix an installer problem with a server-side change? Message-ID: <2069914337.3902671.1467835883831.JavaMail.zimbra at redhat.com> Content-Type: text/plain; charset=utf-8 Rick, This should be the case for those who hasn't downloaded devsuite directly from developer.redhat.com. Workaround mentioned in documentation should work and I walking throw this workflow from scratch to verify nothing is changed since I did it last time right before summit. Simple test is curl https://username%40mailserver.com:p assword at developers.redhat.com/download-manager/rest/tc-accepted?downloadURL=/file/cdk-2.0.0-beta3.zip works for users previously signed T&C's before download from develoers.redhat.com. Just changing rest would not work as I understand, because additional information in profile is required before developer with developer.redhat.com account can proceed with T&C's signing. Denis -------------- next part -------------- An HTML attachment was scrubbed... URL: From degolovi at redhat.com Wed Jul 6 22:37:02 2016 From: degolovi at redhat.com (Denis Golovin) Date: Wed, 6 Jul 2016 18:37:02 -0400 (EDT) Subject: [Devtools] Fix an installer problem with a server-side change? In-Reply-To: References: Message-ID: <93417907.3928289.1467844622630.JavaMail.zimbra@redhat.com> Rick, minor correction for curl command. It should be issued with -s option to suppress progress bar. The output would be true/false/Invalid user credentials for user username at mailserver.com. Denis ----- Original Message ----- > From: "Rick Wagner" > To: devtools at redhat.com, "Denis Golovin" > Sent: Wednesday, July 6, 2016 2:03:49 PM > Subject: Re: [Devtools] Fix an installer problem with a server-side change? > > Hi Denis, > > Thanks much for that idea. > > I've written our customers, let's see if they can coax a 'true' out of > curl. That may help us get to the bottom of the problem, let's see. > > Rick > > ------------------------------ > > Message: 6 > Date: Wed, 6 Jul 2016 16:11:23 -0400 (EDT) > From: Denis Golovin > To: Rick Wagner > Cc: devtools at redhat.com > Subject: Re: [Devtools] Fix an installer problem with a server-side > change? > Message-ID: > <2069914337.3902671.1467835883831.JavaMail.zimbra at redhat.com> > Content-Type: text/plain; charset=utf-8 > > Rick, > > This should be the case for those who hasn't downloaded devsuite directly > from > developer.redhat.com. Workaround mentioned in documentation should work and > I walking > throw this workflow from scratch to verify nothing is changed since I did > it last time > right before summit. > > Simple test is > > curl https://username%40mailserver.com:p > assword at developers.redhat.com/download-manager/rest/tc-accepted?downloadURL=/file/cdk-2.0.0-beta3.zip > > works for users previously signed T&C's before download from > develoers.redhat.com. > > > Just changing rest would not work as I understand, because additional > information in > profile is required before developer with developer.redhat.com account can > proceed with > T&C's signing. > > > Denis > From degolovi at redhat.com Thu Jul 7 00:18:39 2016 From: degolovi at redhat.com (Denis Golovin) Date: Wed, 6 Jul 2016 20:18:39 -0400 (EDT) Subject: [Devtools] Fix an installer problem with a server-side change? In-Reply-To: <93417907.3928289.1467844622630.JavaMail.zimbra@redhat.com> References: <93417907.3928289.1467844622630.JavaMail.zimbra@redhat.com> Message-ID: <1582948441.3940414.1467850719230.JavaMail.zimbra@redhat.com> Rick devsuite installer supports only users with Red Hat Developer Account. it means registration with social account doesn't work. Workaround would be: 1. Visit registration here https://developers.redhat.com/auth/realms/rhd/login-actions/registration?code=rAAJsUjKrvSMRBFSY5mpfvp87g9LS8Xub8_bjkj7lvI.68060bb4-4525-4f5f-98aa-98651b2fab74 2. then use e-mail/password in devsuite installer Denis ----- Original Message ----- > From: "Denis Golovin" > To: "Rick Wagner" > Cc: devtools at redhat.com > Sent: Wednesday, July 6, 2016 3:37:02 PM > Subject: Re: [Devtools] Fix an installer problem with a server-side change? > > Rick, > > minor correction for curl command. It should be issued with -s option to > suppress progress bar. > The output would be true/false/Invalid user credentials for user > username at mailserver.com. > > Denis > > > ----- Original Message ----- > > From: "Rick Wagner" > > To: devtools at redhat.com, "Denis Golovin" > > Sent: Wednesday, July 6, 2016 2:03:49 PM > > Subject: Re: [Devtools] Fix an installer problem with a server-side change? > > > > Hi Denis, > > > > Thanks much for that idea. > > > > I've written our customers, let's see if they can coax a 'true' out of > > curl. That may help us get to the bottom of the problem, let's see. > > > > Rick > > > > ------------------------------ > > > > Message: 6 > > Date: Wed, 6 Jul 2016 16:11:23 -0400 (EDT) > > From: Denis Golovin > > To: Rick Wagner > > Cc: devtools at redhat.com > > Subject: Re: [Devtools] Fix an installer problem with a server-side > > change? > > Message-ID: > > <2069914337.3902671.1467835883831.JavaMail.zimbra at redhat.com> > > Content-Type: text/plain; charset=utf-8 > > > > Rick, > > > > This should be the case for those who hasn't downloaded devsuite directly > > from > > developer.redhat.com. Workaround mentioned in documentation should work and > > I walking > > throw this workflow from scratch to verify nothing is changed since I did > > it last time > > right before summit. > > > > Simple test is > > > > curl https://username%40mailserver.com:p > > assword at developers.redhat.com/download-manager/rest/tc-accepted?downloadURL=/file/cdk-2.0.0-beta3.zip > > > > works for users previously signed T&C's before download from > > develoers.redhat.com. > > > > > > Just changing rest would not work as I understand, because additional > > information in > > profile is required before developer with developer.redhat.com account can > > proceed with > > T&C's signing. > > > > > > Denis > > > > _______________________________________________ > Devtools mailing list > Devtools at redhat.com > https://www.redhat.com/mailman/listinfo/devtools > From mhusnain at redhat.com Thu Jul 7 00:32:06 2016 From: mhusnain at redhat.com (Misha Husnain Ali) Date: Thu, 7 Jul 2016 10:32:06 +1000 Subject: [Devtools] Development Suite installation question - C/O SME with knowledge of installer edits In-Reply-To: <573810996.3897959.1467833884253.JavaMail.zimbra@redhat.com> References: <4892002.EmcPcHGPPG@x230> <573810996.3897959.1467833884253.JavaMail.zimbra@redhat.com> Message-ID: I remember this issue. Is there any way we can identify the paths leading up to this problem and comprehensively test them to provide clear aid to users who may encounter this issue? I'm happy to volunteer to test some of them if we can identify the various paths users may take. -- Misha Husnain Ali Technical Writer 2, CCS Brisbane On Thu, Jul 7, 2016 at 5:38 AM, Denis Golovin wrote: > T&C's signing workflow is not user friendly ATM. > > Workaround mentioned in https://access.redhat.com/articles/2360571 worked > before for > many dev's who was testing installer. I am going to do check full T&C's > signing again today > and send update ASAP. > > This problem should be affecting only customers who didn't get installer > directly from develper.redhat.com > download. > > Denis > > ----- Original Message ----- > > From: "Robert Kratky" > > To: devtools at redhat.com > > Cc: "Rick Wagner" > > Sent: Wednesday, July 6, 2016 8:51:03 AM > > Subject: Re: [Devtools] Development Suite installation question - C/O > SME with knowledge of installer edits > > > > On 6.?7.?2016 10:08:09, Rick Wagner wrote: > > > > > Hello DevTools, > > > > > > We have a customer case that deals with the error message "Terms and > > > Conditions for the CDK have not been signed". (Actually, this is the > > > second case in 2 days for this problem.) > > > > > > The customer has tried the suggested workaround, without satisfactory > > > results. ("This error appears on the *Log In* page when starting the > > > Installer. To fix the problem, start downloading the Installer to > ensure > > > the *Terms and Conditions* are viewed and accepted and then cancel the > > > binary download." We offer this suggestion in the knowledge article at > > > [1].) > > > > > > Can a knowledgeable SME please offer ideas about alternative courses of > > > action? > > > > Hi Rick, > > > > The problem happens quite often, apparently. I asked about this last > Friday > > in devtools-program [a] -- on behalf of a user who reported the problem > in a > > comment under the old version of the Kbase article [b]. > > > > Any workaround would be appreciated. > > > > Thanks. > > > > Robert > > > > [a] > > > http://post-office.corp.redhat.com/archives/devtools-program/2016-July/msg00001.html > > [b] https://access.redhat.com/articles/2255391#comment-1066361 > > > > > Extra credit: Can you please point me to the source code that produces > > > this edit error? A little spelunking by the Support team sometimes > helps > > > with related issues. > > > > > > Thanks! > > > > > > Rick > > > > > > [1] https://access.redhat.com/articles/2360571 > > > > > > _______________________________________________ > > 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 Thu Jul 7 08:24:41 2016 From: jdyson at redhat.com (Jimmi Dyson) Date: Thu, 7 Jul 2016 09:24:41 +0100 Subject: [Devtools] support for OpenShift Container Platform / Origin in minikube? In-Reply-To: <20160706073224.GE96345@nineveh.lan> References: <34C29FC6-B5F2-439B-95F4-2D42A156E35E@redhat.com> <217D53D0-D256-48E5-8D26-CFD36BF44AC7@redhat.com> <20160706073224.GE96345@nineveh.lan> Message-ID: I've started minishift (fork of minikube) at https://github.com/jimmidyson/minishift if anyone wants to try it out. Will publish a first release of it later today or tomorrow hopefully. All feedback welcome - building is pretty simple, as long as you have the Go toolchain setup. > would this be able to run red hat's variation of docker ? Of course we can but the question is what benefit it brings? As this is only for single dev, easy getting started & play what Docker version is being used should be inconsequential to the ux. The only problem I can see with using RHT's Docker is the size of the ISO that minishift will need to download to start the VM. Right now this is ~36MB & this allows for really speedy startup (effectively no waiting for download). Switching to RHT's Docker & potentially CentOS/RHEL I would expect this to grow, which isn't terrible but would affect the ux somewhat. > and how about openshift itself ? Minishift runs latest version of OpenShift (latest version at time of build embedded in the minishift binary for speedy start up time) & I am going to make the version configurable via flags which will download the specified release from github on startup, with caching for subsequent runs, etc. Thanks, Jimmi On 6 July 2016 at 08:32, Hardy Ferentschik wrote: > On Wed, 06-Jul-2016 00:53, Max Rydahl Andersen wrote: >> looks great. would this be able to run red hat's variation of docker ? and >> how about openshift itself ? > > My thinking as well. Might be worth investigating. A miniopenshift would have > a great appeal. > > --Hardy > From rhuss at redhat.com Thu Jul 7 08:38:49 2016 From: rhuss at redhat.com (Roland Huss) Date: Thu, 7 Jul 2016 10:38:49 +0200 Subject: [Devtools] support for OpenShift Container Platform / Origin in minikube? In-Reply-To: References: <34C29FC6-B5F2-439B-95F4-2D42A156E35E@redhat.com> <217D53D0-D256-48E5-8D26-CFD36BF44AC7@redhat.com> <20160706073224.GE96345@nineveh.lan> Message-ID: <519c466c-c4d8-3880-2d1e-4078ef43e697@redhat.com> I had the luck to try it out first and I have to say, it's awesome. From scratch to a running OpenShift origin with minishift it took me 1:56 min (11 MBit/s downstream) for the initial run and 30s for subsequent starts. On OS X it uses xhyve under the covers so not even VirtualBox is required (an no local Docker installation, btw). Kudos Jimmi, it's really extraordinary ! imo that the way to go for competing the outstanding Docker Inc. UX .... ... roland > I've started minishift (fork of minikube) at > https://github.com/jimmidyson/minishift if anyone wants to try it out. > Will publish a first release of it later today or tomorrow hopefully. > All feedback welcome - building is pretty simple, as long as you have > the Go toolchain setup. > >> would this be able to run red hat's variation of docker ? > > Of course we can but the question is what benefit it brings? As this > is only for single dev, easy getting started & play what Docker > version is being used should be inconsequential to the ux. The only > problem I can see with using RHT's Docker is the size of the ISO that > minishift will need to download to start the VM. Right now this is > ~36MB & this allows for really speedy startup (effectively no waiting > for download). Switching to RHT's Docker & potentially CentOS/RHEL I > would expect this to grow, which isn't terrible but would affect the > ux somewhat. > >> and how about openshift itself ? > > Minishift runs latest version of OpenShift (latest version at time of > build embedded in the minishift binary for speedy start up time) & I > am going to make the version configurable via flags which will > download the specified release from github on startup, with caching > for subsequent runs, etc. > > Thanks, > Jimmi > > On 6 July 2016 at 08:32, Hardy Ferentschik wrote: >> On Wed, 06-Jul-2016 00:53, Max Rydahl Andersen wrote: >>> looks great. would this be able to run red hat's variation of docker ? and >>> how about openshift itself ? >> >> My thinking as well. Might be worth investigating. A miniopenshift would have >> a great appeal. >> >> --Hardy >> > > _______________________________________________ > Devtools mailing list > Devtools at redhat.com > https://www.redhat.com/mailman/listinfo/devtools > From hferents at redhat.com Thu Jul 7 09:30:14 2016 From: hferents at redhat.com (Hardy Ferentschik) Date: Thu, 7 Jul 2016 11:30:14 +0200 Subject: [Devtools] support for OpenShift Container Platform / Origin in minikube? In-Reply-To: <519c466c-c4d8-3880-2d1e-4078ef43e697@redhat.com> References: <34C29FC6-B5F2-439B-95F4-2D42A156E35E@redhat.com> <217D53D0-D256-48E5-8D26-CFD36BF44AC7@redhat.com> <20160706073224.GE96345@nineveh.lan> <519c466c-c4d8-3880-2d1e-4078ef43e697@redhat.com> Message-ID: <20160707093014.GC6387@nineveh.lan> Hi, On Thu, 07-Jul-2016 10:38, Roland Huss wrote: > I had the luck to try it out first and I have to say, it's awesome. From > scratch to a running OpenShift origin with minishift it took me 1:56 min > (11 MBit/s downstream) for the initial run and 30s for subsequent starts. That is absolutely amazing. I cannot wait to try the release once it is out. > On OS X it uses xhyve under the covers so not even VirtualBox is > required (an no local Docker installation, btw). :-) > Kudos Jimmi, it's really extraordinary ! So where does this leave us with ADB? If minishift gets traction I have a hard time seeing people wanting to use ADB. --Hardy -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 496 bytes Desc: not available URL: From prkumar at redhat.com Thu Jul 7 10:49:24 2016 From: prkumar at redhat.com (Praveen Kumar) Date: Thu, 7 Jul 2016 16:19:24 +0530 Subject: [Devtools] support for OpenShift Container Platform / Origin in minikube? In-Reply-To: <20160707093014.GC6387@nineveh.lan> References: <34C29FC6-B5F2-439B-95F4-2D42A156E35E@redhat.com> <217D53D0-D256-48E5-8D26-CFD36BF44AC7@redhat.com> <20160706073224.GE96345@nineveh.lan> <519c466c-c4d8-3880-2d1e-4078ef43e697@redhat.com> <20160707093014.GC6387@nineveh.lan> Message-ID: On Thu, Jul 7, 2016 at 3:00 PM, Hardy Ferentschik wrote: > Hi, > > On Thu, 07-Jul-2016 10:38, Roland Huss wrote: >> I had the luck to try it out first and I have to say, it's awesome. From >> scratch to a running OpenShift origin with minishift it took me 1:56 min >> (11 MBit/s downstream) for the initial run and 30s for subsequent starts. Really Great !! > > That is absolutely amazing. I cannot wait to try the release once it is out. > >> On OS X it uses xhyve under the covers so not even VirtualBox is >> required (an no local Docker installation, btw). > > :-) > >> Kudos Jimmi, it's really extraordinary ! > > So where does this leave us with ADB? If minishift gets traction I have a hard > time seeing people wanting to use ADB. I do have same question for CDK because if we can integrate origin then it is just matter of binaries (which are part of OSE). Tooling which are consuming CDK today can be integrated with minishift (just expose required env). Currently CDK have options for kubernetes and OpenShift but again our target is to put OpenShift first choice. Thoughts ? -- Praveen Kumar https://fedoraproject.org/wiki/User:Kumarpraveen From pmuir at redhat.com Thu Jul 7 11:17:22 2016 From: pmuir at redhat.com (Pete Muir) Date: Thu, 7 Jul 2016 12:17:22 +0100 Subject: [Devtools] support for OpenShift Container Platform / Origin in minikube? In-Reply-To: References: <34C29FC6-B5F2-439B-95F4-2D42A156E35E@redhat.com> <217D53D0-D256-48E5-8D26-CFD36BF44AC7@redhat.com> <20160706073224.GE96345@nineveh.lan> <519c466c-c4d8-3880-2d1e-4078ef43e697@redhat.com> <20160707093014.GC6387@nineveh.lan> Message-ID: On 7 July 2016 at 11:49, Praveen Kumar wrote: > On Thu, Jul 7, 2016 at 3:00 PM, Hardy Ferentschik wrote: >> Hi, >> >> On Thu, 07-Jul-2016 10:38, Roland Huss wrote: >>> I had the luck to try it out first and I have to say, it's awesome. From >>> scratch to a running OpenShift origin with minishift it took me 1:56 min >>> (11 MBit/s downstream) for the initial run and 30s for subsequent starts. > > Really Great !! > >> >> That is absolutely amazing. I cannot wait to try the release once it is out. >> >>> On OS X it uses xhyve under the covers so not even VirtualBox is >>> required (an no local Docker installation, btw). >> >> :-) >> >>> Kudos Jimmi, it's really extraordinary ! >> >> So where does this leave us with ADB? If minishift gets traction I have a hard >> time seeing people wanting to use ADB. > > I do have same question for CDK because if we can integrate origin > then it is just matter of binaries (which are part of OSE). Tooling > which are consuming CDK today can be integrated with minishift (just > expose required env). Currently CDK have options for kubernetes and > OpenShift but again our target is to put OpenShift first choice. We would still want to ship a product version (using RHEL/OpenShift Container Platform etc.) Mini* could be components of this product. > > Thoughts ? > > -- > Praveen Kumar > https://fedoraproject.org/wiki/User:Kumarpraveen > > _______________________________________________ > Devtools mailing list > Devtools at redhat.com > https://www.redhat.com/mailman/listinfo/devtools From pmuir at redhat.com Thu Jul 7 11:40:03 2016 From: pmuir at redhat.com (Pete Muir) Date: Thu, 7 Jul 2016 12:40:03 +0100 Subject: [Devtools] Fix an installer problem with a server-side change? In-Reply-To: <1582948441.3940414.1467850719230.JavaMail.zimbra@redhat.com> References: <93417907.3928289.1467844622630.JavaMail.zimbra@redhat.com> <1582948441.3940414.1467850719230.JavaMail.zimbra@redhat.com> Message-ID: Denis, are you sure about this? The social account login should generate a full user, if you do proceed to initiate a download of the installer. On 7 July 2016 at 01:18, Denis Golovin wrote: > Rick > > devsuite installer supports only users with Red Hat Developer Account. > it means registration with social account doesn't work. > > Workaround would be: > 1. Visit registration here > https://developers.redhat.com/auth/realms/rhd/login-actions/registration?code=rAAJsUjKrvSMRBFSY5mpfvp87g9LS8Xub8_bjkj7lvI.68060bb4-4525-4f5f-98aa-98651b2fab74 > 2. then use e-mail/password in devsuite installer > > Denis > > ----- Original Message ----- >> From: "Denis Golovin" >> To: "Rick Wagner" >> Cc: devtools at redhat.com >> Sent: Wednesday, July 6, 2016 3:37:02 PM >> Subject: Re: [Devtools] Fix an installer problem with a server-side change? >> >> Rick, >> >> minor correction for curl command. It should be issued with -s option to >> suppress progress bar. >> The output would be true/false/Invalid user credentials for user >> username at mailserver.com. >> >> Denis >> >> >> ----- Original Message ----- >> > From: "Rick Wagner" >> > To: devtools at redhat.com, "Denis Golovin" >> > Sent: Wednesday, July 6, 2016 2:03:49 PM >> > Subject: Re: [Devtools] Fix an installer problem with a server-side change? >> > >> > Hi Denis, >> > >> > Thanks much for that idea. >> > >> > I've written our customers, let's see if they can coax a 'true' out of >> > curl. That may help us get to the bottom of the problem, let's see. >> > >> > Rick >> > >> > ------------------------------ >> > >> > Message: 6 >> > Date: Wed, 6 Jul 2016 16:11:23 -0400 (EDT) >> > From: Denis Golovin >> > To: Rick Wagner >> > Cc: devtools at redhat.com >> > Subject: Re: [Devtools] Fix an installer problem with a server-side >> > change? >> > Message-ID: >> > <2069914337.3902671.1467835883831.JavaMail.zimbra at redhat.com> >> > Content-Type: text/plain; charset=utf-8 >> > >> > Rick, >> > >> > This should be the case for those who hasn't downloaded devsuite directly >> > from >> > developer.redhat.com. Workaround mentioned in documentation should work and >> > I walking >> > throw this workflow from scratch to verify nothing is changed since I did >> > it last time >> > right before summit. >> > >> > Simple test is >> > >> > curl https://username%40mailserver.com:p >> > assword at developers.redhat.com/download-manager/rest/tc-accepted?downloadURL=/file/cdk-2.0.0-beta3.zip >> > >> > works for users previously signed T&C's before download from >> > develoers.redhat.com. >> > >> > >> > Just changing rest would not work as I understand, because additional >> > information in >> > profile is required before developer with developer.redhat.com account can >> > proceed with >> > T&C's signing. >> > >> > >> > Denis >> > >> >> _______________________________________________ >> 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 From pmuir at redhat.com Thu Jul 7 11:40:54 2016 From: pmuir at redhat.com (Pete Muir) Date: Thu, 7 Jul 2016 12:40:54 +0100 Subject: [Devtools] Fix an installer problem with a server-side change? In-Reply-To: References: Message-ID: On 6 July 2016 at 20:02, Rick Wagner wrote: > Hello DevTools, > > It seems we have a problem with the current version of the Development Suite > installer. We have at least 2 new customer cases reporting inability to > install due to the message dialogue "Terms and Conditions for the CDK have > not been signed". > > This is concerning because we're also seeing similar activity on non-support > channels. It's also worth noting that not every user that has a problem > reports it-- some just give up and move on. There is enough volume here > that we probably should treat this with some urgency. > > It seems likely the relevant code (thanks for highlighting this, Alexey) is > below: > > ------------------------------------------------- > > login() { > this.authFailed = false; > this.tandcNotSigned = false; > > let req = { > method: 'GET', > url: > 'https://developers.redhat.com/download-manager/rest/tc-accepted?downloadURL=/file/cdk-2.0.0-beta3.zip', > <<<<<<<<<---- returns 'false' when not approved I noticed when reading this that this code appears to be downloading CDK 2.0.0-beta3 which implies that either this is an old version of the installer, or the installer is installing a very old CDK... > headers: { > 'Authorization': 'Basic ' + this.base64.encode(this.username + ':' + > this.password) > } > }; > > this.http(req) > .then(this.handleHttpSuccess.bind(this)) > .catch(this.handleHttpFailure.bind(this)); > } > > --------------------------------- > > > So we have users getting denied use of our product. Do we require a rebuild > immediately? Maybe. > > How about if we changed the rest service > (https://developers.redhat.com/download-manager/rest/tc-accepted) so it > includes a peak at an override database as well as whatever it's currently > doing now? > > In that way, we could have the users pop over to a 'yes, I agree to the > terms' page to insert an entry into the database. The rest service could > use something like the provided username as a key to ensure a 'true' is > returned. > > > Or not. Is there a better way to fix this? > > Please consider, we need to fix this sooner rather than later.... > > Thanks, > > Rick > > > _______________________________________________ > Devtools mailing list > Devtools at redhat.com > https://www.redhat.com/mailman/listinfo/devtools > From ppitonak at redhat.com Thu Jul 7 11:50:19 2016 From: ppitonak at redhat.com (Pavol Pitonak) Date: Thu, 7 Jul 2016 13:50:19 +0200 Subject: [Devtools] Fix an installer problem with a server-side change? In-Reply-To: References: Message-ID: It's not installing CDK 2.0.0-beta3 but the one specified in [1]. The mentioned URL is only used for finding out whether the user provided correct username/password and whether he had agreed with T&C. [1] https://github.com/redhat-developer-tooling/developer-platform-install/blob/master/requirements.json#L7 On Thu, Jul 7, 2016 at 1:40 PM, Pete Muir wrote: > On 6 July 2016 at 20:02, Rick Wagner wrote: > > Hello DevTools, > > > > It seems we have a problem with the current version of the Development > Suite > > installer. We have at least 2 new customer cases reporting inability to > > install due to the message dialogue "Terms and Conditions for the CDK > have > > not been signed". > > > > This is concerning because we're also seeing similar activity on > non-support > > channels. It's also worth noting that not every user that has a problem > > reports it-- some just give up and move on. There is enough volume here > > that we probably should treat this with some urgency. > > > > It seems likely the relevant code (thanks for highlighting this, Alexey) > is > > below: > > > > ------------------------------------------------- > > > > login() { > > this.authFailed = false; > > this.tandcNotSigned = false; > > > > let req = { > > method: 'GET', > > url: > > ' > https://developers.redhat.com/download-manager/rest/tc-accepted?downloadURL=/file/cdk-2.0.0-beta3.zip > ', > > <<<<<<<<<---- returns 'false' when not approved > > I noticed when reading this that this code appears to be downloading > CDK 2.0.0-beta3 which implies that either this is an old version of > the installer, or the installer is installing a very old CDK... > > > headers: { > > 'Authorization': 'Basic ' + this.base64.encode(this.username + > ':' + > > this.password) > > } > > }; > > > > this.http(req) > > .then(this.handleHttpSuccess.bind(this)) > > .catch(this.handleHttpFailure.bind(this)); > > } > > > > --------------------------------- > > > > > > So we have users getting denied use of our product. Do we require a > rebuild > > immediately? Maybe. > > > > How about if we changed the rest service > > (https://developers.redhat.com/download-manager/rest/tc-accepted) so it > > includes a peak at an override database as well as whatever it's > currently > > doing now? > > > > In that way, we could have the users pop over to a 'yes, I agree to the > > terms' page to insert an entry into the database. The rest service could > > use something like the provided username as a key to ensure a 'true' is > > returned. > > > > > > Or not. Is there a better way to fix this? > > > > Please consider, we need to fix this sooner rather than later.... > > > > Thanks, > > > > Rick > > > > > > _______________________________________________ > > 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 pmuir at redhat.com Thu Jul 7 11:58:23 2016 From: pmuir at redhat.com (Pete Muir) Date: Thu, 7 Jul 2016 12:58:23 +0100 Subject: [Devtools] Fix an installer problem with a server-side change? In-Reply-To: References: Message-ID: We recently archived the cdk 2.0 in the download manager, so it's possible that this is now returning false regardless of sub status. Are we sure this URL ever returns true? Also, this seems like a very fragile way to do the check. Do we have a plan to do it properly? On 7 Jul 2016 12:50 p.m., "Pavol Pitonak" wrote: > It's not installing CDK 2.0.0-beta3 but the one specified in [1]. The > mentioned URL is only used for finding out whether the user provided > correct username/password and whether he had agreed with T&C. > > [1] > https://github.com/redhat-developer-tooling/developer-platform-install/blob/master/requirements.json#L7 > > On Thu, Jul 7, 2016 at 1:40 PM, Pete Muir wrote: > >> On 6 July 2016 at 20:02, Rick Wagner wrote: >> > Hello DevTools, >> > >> > It seems we have a problem with the current version of the Development >> Suite >> > installer. We have at least 2 new customer cases reporting inability to >> > install due to the message dialogue "Terms and Conditions for the CDK >> have >> > not been signed". >> > >> > This is concerning because we're also seeing similar activity on >> non-support >> > channels. It's also worth noting that not every user that has a problem >> > reports it-- some just give up and move on. There is enough volume here >> > that we probably should treat this with some urgency. >> > >> > It seems likely the relevant code (thanks for highlighting this, >> Alexey) is >> > below: >> > >> > ------------------------------------------------- >> > >> > login() { >> > this.authFailed = false; >> > this.tandcNotSigned = false; >> > >> > let req = { >> > method: 'GET', >> > url: >> > ' >> https://developers.redhat.com/download-manager/rest/tc-accepted?downloadURL=/file/cdk-2.0.0-beta3.zip >> ', >> > <<<<<<<<<---- returns 'false' when not approved >> >> I noticed when reading this that this code appears to be downloading >> CDK 2.0.0-beta3 which implies that either this is an old version of >> the installer, or the installer is installing a very old CDK... >> >> > headers: { >> > 'Authorization': 'Basic ' + this.base64.encode(this.username + >> ':' + >> > this.password) >> > } >> > }; >> > >> > this.http(req) >> > .then(this.handleHttpSuccess.bind(this)) >> > .catch(this.handleHttpFailure.bind(this)); >> > } >> > >> > --------------------------------- >> > >> > >> > So we have users getting denied use of our product. Do we require a >> rebuild >> > immediately? Maybe. >> > >> > How about if we changed the rest service >> > (https://developers.redhat.com/download-manager/rest/tc-accepted) so it >> > includes a peak at an override database as well as whatever it's >> currently >> > doing now? >> > >> > In that way, we could have the users pop over to a 'yes, I agree to the >> > terms' page to insert an entry into the database. The rest service >> could >> > use something like the provided username as a key to ensure a 'true' is >> > returned. >> > >> > >> > Or not. Is there a better way to fix this? >> > >> > Please consider, we need to fix this sooner rather than later.... >> > >> > Thanks, >> > >> > Rick >> > >> > >> > _______________________________________________ >> > 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 ppitonak at redhat.com Thu Jul 7 12:05:32 2016 From: ppitonak at redhat.com (Pavol Pitonak) Date: Thu, 7 Jul 2016 14:05:32 +0200 Subject: [Devtools] Fix an installer problem with a server-side change? In-Reply-To: References: Message-ID: Yes, it does return true for my credentials. On Thu, Jul 7, 2016 at 1:58 PM, Pete Muir wrote: > We recently archived the cdk 2.0 in the download manager, so it's possible > that this is now returning false regardless of sub status. Are we sure this > URL ever returns true? > > Also, this seems like a very fragile way to do the check. Do we have a > plan to do it properly? > On 7 Jul 2016 12:50 p.m., "Pavol Pitonak" wrote: > >> It's not installing CDK 2.0.0-beta3 but the one specified in [1]. The >> mentioned URL is only used for finding out whether the user provided >> correct username/password and whether he had agreed with T&C. >> >> [1] >> https://github.com/redhat-developer-tooling/developer-platform-install/blob/master/requirements.json#L7 >> >> On Thu, Jul 7, 2016 at 1:40 PM, Pete Muir wrote: >> >>> On 6 July 2016 at 20:02, Rick Wagner wrote: >>> > Hello DevTools, >>> > >>> > It seems we have a problem with the current version of the Development >>> Suite >>> > installer. We have at least 2 new customer cases reporting inability >>> to >>> > install due to the message dialogue "Terms and Conditions for the CDK >>> have >>> > not been signed". >>> > >>> > This is concerning because we're also seeing similar activity on >>> non-support >>> > channels. It's also worth noting that not every user that has a >>> problem >>> > reports it-- some just give up and move on. There is enough volume >>> here >>> > that we probably should treat this with some urgency. >>> > >>> > It seems likely the relevant code (thanks for highlighting this, >>> Alexey) is >>> > below: >>> > >>> > ------------------------------------------------- >>> > >>> > login() { >>> > this.authFailed = false; >>> > this.tandcNotSigned = false; >>> > >>> > let req = { >>> > method: 'GET', >>> > url: >>> > ' >>> https://developers.redhat.com/download-manager/rest/tc-accepted?downloadURL=/file/cdk-2.0.0-beta3.zip >>> ', >>> > <<<<<<<<<---- returns 'false' when not approved >>> >>> I noticed when reading this that this code appears to be downloading >>> CDK 2.0.0-beta3 which implies that either this is an old version of >>> the installer, or the installer is installing a very old CDK... >>> >>> > headers: { >>> > 'Authorization': 'Basic ' + this.base64.encode(this.username + >>> ':' + >>> > this.password) >>> > } >>> > }; >>> > >>> > this.http(req) >>> > .then(this.handleHttpSuccess.bind(this)) >>> > .catch(this.handleHttpFailure.bind(this)); >>> > } >>> > >>> > --------------------------------- >>> > >>> > >>> > So we have users getting denied use of our product. Do we require a >>> rebuild >>> > immediately? Maybe. >>> > >>> > How about if we changed the rest service >>> > (https://developers.redhat.com/download-manager/rest/tc-accepted) so >>> it >>> > includes a peak at an override database as well as whatever it's >>> currently >>> > doing now? >>> > >>> > In that way, we could have the users pop over to a 'yes, I agree to the >>> > terms' page to insert an entry into the database. The rest service >>> could >>> > use something like the provided username as a key to ensure a 'true' is >>> > returned. >>> > >>> > >>> > Or not. Is there a better way to fix this? >>> > >>> > Please consider, we need to fix this sooner rather than later.... >>> > >>> > Thanks, >>> > >>> > Rick >>> > >>> > >>> > _______________________________________________ >>> > 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 rwagner at redhat.com Thu Jul 7 12:12:55 2016 From: rwagner at redhat.com (Rick Wagner) Date: Thu, 7 Jul 2016 07:12:55 -0500 Subject: [Devtools] Fix an installer problem with a server-side change? In-Reply-To: <1582948441.3940414.1467850719230.JavaMail.zimbra@redhat.com> References: <93417907.3928289.1467844622630.JavaMail.zimbra@redhat.com> <1582948441.3940414.1467850719230.JavaMail.zimbra@redhat.com> Message-ID: Hi Denis, That link gets me an error page that reads "We're sorry.... An error occurred, please login again through your application". Do we expect the customers with failing installations will have a different result? Thanks, Rick On Wed, Jul 6, 2016 at 7:18 PM, Denis Golovin wrote: > Rick > > devsuite installer supports only users with Red Hat Developer Account. > it means registration with social account doesn't work. > > Workaround would be: > 1. Visit registration here > > https://developers.redhat.com/auth/realms/rhd/login-actions/registration?code=rAAJsUjKrvSMRBFSY5mpfvp87g9LS8Xub8_bjkj7lvI.68060bb4-4525-4f5f-98aa-98651b2fab74 > 2. then use e-mail/password in devsuite installer > > Denis > > ----- Original Message ----- > > From: "Denis Golovin" > > To: "Rick Wagner" > > Cc: devtools at redhat.com > > Sent: Wednesday, July 6, 2016 3:37:02 PM > > Subject: Re: [Devtools] Fix an installer problem with a server-side > change? > > > > Rick, > > > > minor correction for curl command. It should be issued with -s option to > > suppress progress bar. > > The output would be true/false/Invalid user credentials for user > > username at mailserver.com. > > > > Denis > > > > > > ----- Original Message ----- > > > From: "Rick Wagner" > > > To: devtools at redhat.com, "Denis Golovin" > > > Sent: Wednesday, July 6, 2016 2:03:49 PM > > > Subject: Re: [Devtools] Fix an installer problem with a server-side > change? > > > > > > Hi Denis, > > > > > > Thanks much for that idea. > > > > > > I've written our customers, let's see if they can coax a 'true' out of > > > curl. That may help us get to the bottom of the problem, let's see. > > > > > > Rick > > > > > > ------------------------------ > > > > > > Message: 6 > > > Date: Wed, 6 Jul 2016 16:11:23 -0400 (EDT) > > > From: Denis Golovin > > > To: Rick Wagner > > > Cc: devtools at redhat.com > > > Subject: Re: [Devtools] Fix an installer problem with a server-side > > > change? > > > Message-ID: > > > <2069914337.3902671.1467835883831.JavaMail.zimbra at redhat.com> > > > Content-Type: text/plain; charset=utf-8 > > > > > > Rick, > > > > > > This should be the case for those who hasn't downloaded devsuite > directly > > > from > > > developer.redhat.com. Workaround mentioned in documentation should > work and > > > I walking > > > throw this workflow from scratch to verify nothing is changed since I > did > > > it last time > > > right before summit. > > > > > > Simple test is > > > > > > curl https://username%40mailserver.com:p > > > > assword at developers.redhat.com/download-manager/rest/tc-accepted?downloadURL=/file/cdk-2.0.0-beta3.zip > > > > > > works for users previously signed T&C's before download from > > > develoers.redhat.com. > > > > > > > > > Just changing rest would not work as I understand, because additional > > > information in > > > profile is required before developer with developer.redhat.com > account can > > > proceed with > > > T&C's signing. > > > > > > > > > Denis > > > > > > > _______________________________________________ > > Devtools mailing list > > Devtools at redhat.com > > https://www.redhat.com/mailman/listinfo/devtools > > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From rkratky at redhat.com Thu Jul 7 13:38:18 2016 From: rkratky at redhat.com (Robert Kratky) Date: Thu, 07 Jul 2016 15:38:18 +0200 Subject: [Devtools] Development Suite installation question - C/O SME with knowledge of installer edits In-Reply-To: References: <573810996.3897959.1467833884253.JavaMail.zimbra@redhat.com> Message-ID: <11841544.Z7WsqPLCK5@x230> I updated the trouleshooting section in [1] based on the discussion during today's program call. Please, have a look and let me know if what I wrote is accurate -- I cannot test at this moment. This is what it says now: ............. Terms and Conditions Error Error: ?Terms and Conditions for CDK have not been signed? This error appears on the Log In page when starting the Installer. To work around the problem, log in to the Developer Portal using your Red Hat credentials -- the credentials that you created either on redhat.com or developers.redhat.com. Do not use your social accounts to log in. Then start downloading the Installer from Red Hat Development Suite download page. If you do not have a Red Hat account, create one at developers.redhat.com. ............. Thanks. Robert [1] https://access.redhat.com/articles/2360571#troubleshooting On 7.?7.?2016 10:32:06, Misha Husnain Ali wrote: > I remember this issue. Is there any way we can identify the paths leading > up to this problem and comprehensively test them to provide clear aid to > users who may encounter this issue? I'm happy to volunteer to test some of > them if we can identify the various paths users may take. > > > -- > Misha Husnain Ali > Technical Writer 2, CCS Brisbane > > On Thu, Jul 7, 2016 at 5:38 AM, Denis Golovin wrote: > > > T&C's signing workflow is not user friendly ATM. > > > > Workaround mentioned in https://access.redhat.com/articles/2360571 worked > > before for > > many dev's who was testing installer. I am going to do check full T&C's > > signing again today > > and send update ASAP. > > > > This problem should be affecting only customers who didn't get installer > > directly from develper.redhat.com > > download. > > > > Denis > > > > ----- Original Message ----- > > > From: "Robert Kratky" > > > To: devtools at redhat.com > > > Cc: "Rick Wagner" > > > Sent: Wednesday, July 6, 2016 8:51:03 AM > > > Subject: Re: [Devtools] Development Suite installation question - C/O > > SME with knowledge of installer edits > > > > > > On 6.?7.?2016 10:08:09, Rick Wagner wrote: > > > > > > > Hello DevTools, > > > > > > > > We have a customer case that deals with the error message "Terms and > > > > Conditions for the CDK have not been signed". (Actually, this is the > > > > second case in 2 days for this problem.) > > > > > > > > The customer has tried the suggested workaround, without satisfactory > > > > results. ("This error appears on the *Log In* page when starting the > > > > Installer. To fix the problem, start downloading the Installer to > > ensure > > > > the *Terms and Conditions* are viewed and accepted and then cancel the > > > > binary download." We offer this suggestion in the knowledge article at > > > > [1].) > > > > > > > > Can a knowledgeable SME please offer ideas about alternative courses of > > > > action? > > > > > > Hi Rick, > > > > > > The problem happens quite often, apparently. I asked about this last > > Friday > > > in devtools-program [a] -- on behalf of a user who reported the problem > > in a > > > comment under the old version of the Kbase article [b]. > > > > > > Any workaround would be appreciated. > > > > > > Thanks. > > > > > > Robert > > > > > > [a] > > > > > http://post-office.corp.redhat.com/archives/devtools-program/2016-July/msg00001.html > > > [b] https://access.redhat.com/articles/2255391#comment-1066361 > > > > > > > Extra credit: Can you please point me to the source code that produces > > > > this edit error? A little spelunking by the Support team sometimes > > helps > > > > with related issues. > > > > > > > > Thanks! > > > > > > > > Rick > > > > > > > > [1] https://access.redhat.com/articles/2360571 From pmuir at redhat.com Thu Jul 7 13:42:15 2016 From: pmuir at redhat.com (Pete Muir) Date: Thu, 7 Jul 2016 14:42:15 +0100 Subject: [Devtools] Development Suite installation question - C/O SME with knowledge of installer edits In-Reply-To: <11841544.Z7WsqPLCK5@x230> References: <573810996.3897959.1467833884253.JavaMail.zimbra@redhat.com> <11841544.Z7WsqPLCK5@x230> Message-ID: Robert, as discussed on the call, you might want to recommend a "radical" workaround, of just creating a new account entirely, without using social media at all. On 7 July 2016 at 14:38, Robert Kratky wrote: > I updated the trouleshooting section in [1] based on the discussion during today's program call. Please, have a look and let me know if what I wrote is accurate -- I cannot test at this moment. > > This is what it says now: > > ............. > Terms and Conditions Error > > Error: ?Terms and Conditions for CDK have not been signed? > This error appears on the Log In page when starting the Installer. To work around the problem, log in to the Developer Portal using your Red Hat credentials -- the credentials that you created either on redhat.com or developers.redhat.com. Do not use your social accounts to log in. Then start downloading the Installer from Red Hat Development Suite download page. > > If you do not have a Red Hat account, create one at developers.redhat.com. > ............. > > Thanks. > Robert > > [1] https://access.redhat.com/articles/2360571#troubleshooting > > > On 7.?7.?2016 10:32:06, Misha Husnain Ali wrote: > >> I remember this issue. Is there any way we can identify the paths leading >> up to this problem and comprehensively test them to provide clear aid to >> users who may encounter this issue? I'm happy to volunteer to test some of >> them if we can identify the various paths users may take. >> >> >> -- >> Misha Husnain Ali >> Technical Writer 2, CCS Brisbane >> >> On Thu, Jul 7, 2016 at 5:38 AM, Denis Golovin wrote: >> >> > T&C's signing workflow is not user friendly ATM. >> > >> > Workaround mentioned in https://access.redhat.com/articles/2360571 worked >> > before for >> > many dev's who was testing installer. I am going to do check full T&C's >> > signing again today >> > and send update ASAP. >> > >> > This problem should be affecting only customers who didn't get installer >> > directly from develper.redhat.com >> > download. >> > >> > Denis >> > >> > ----- Original Message ----- >> > > From: "Robert Kratky" >> > > To: devtools at redhat.com >> > > Cc: "Rick Wagner" >> > > Sent: Wednesday, July 6, 2016 8:51:03 AM >> > > Subject: Re: [Devtools] Development Suite installation question - C/O >> > SME with knowledge of installer edits >> > > >> > > On 6.?7.?2016 10:08:09, Rick Wagner wrote: >> > > >> > > > Hello DevTools, >> > > > >> > > > We have a customer case that deals with the error message "Terms and >> > > > Conditions for the CDK have not been signed". (Actually, this is the >> > > > second case in 2 days for this problem.) >> > > > >> > > > The customer has tried the suggested workaround, without satisfactory >> > > > results. ("This error appears on the *Log In* page when starting the >> > > > Installer. To fix the problem, start downloading the Installer to >> > ensure >> > > > the *Terms and Conditions* are viewed and accepted and then cancel the >> > > > binary download." We offer this suggestion in the knowledge article at >> > > > [1].) >> > > > >> > > > Can a knowledgeable SME please offer ideas about alternative courses of >> > > > action? >> > > >> > > Hi Rick, >> > > >> > > The problem happens quite often, apparently. I asked about this last >> > Friday >> > > in devtools-program [a] -- on behalf of a user who reported the problem >> > in a >> > > comment under the old version of the Kbase article [b]. >> > > >> > > Any workaround would be appreciated. >> > > >> > > Thanks. >> > > >> > > Robert >> > > >> > > [a] >> > > >> > http://post-office.corp.redhat.com/archives/devtools-program/2016-July/msg00001.html >> > > [b] https://access.redhat.com/articles/2255391#comment-1066361 >> > > >> > > > Extra credit: Can you please point me to the source code that produces >> > > > this edit error? A little spelunking by the Support team sometimes >> > helps >> > > > with related issues. >> > > > >> > > > Thanks! >> > > > >> > > > Rick >> > > > >> > > > [1] https://access.redhat.com/articles/2360571 > > > _______________________________________________ > Devtools mailing list > Devtools at redhat.com > https://www.redhat.com/mailman/listinfo/devtools From rkratky at redhat.com Thu Jul 7 13:58:06 2016 From: rkratky at redhat.com (Robert Kratky) Date: Thu, 07 Jul 2016 15:58:06 +0200 Subject: [Devtools] Development Suite installation question - C/O SME with knowledge of installer edits In-Reply-To: References: <11841544.Z7WsqPLCK5@x230> Message-ID: <1829398.oJedtQYAuc@x230> I updated the text to emphasize that social accounts are not to be used. It now says, basically: 1) log in using RH credentials 2) do not use social accounts 3) if you can't (i.e. you have no RH account), create a new one Robert On 7.?7.?2016 14:42:15, Pete Muir wrote: > Robert, as discussed on the call, you might want to recommend a > "radical" workaround, of just creating a new account entirely, without > using social media at all. > > On 7 July 2016 at 14:38, Robert Kratky wrote: > > I updated the trouleshooting section in [1] based on the discussion during today's program call. Please, have a look and let me know if what I wrote is accurate -- I cannot test at this moment. > > > > This is what it says now: > > > > ............. > > Terms and Conditions Error > > > > Error: ?Terms and Conditions for CDK have not been signed? > > This error appears on the Log In page when starting the Installer. To work around the problem, log in to the Developer Portal using your Red Hat credentials -- the credentials that you created either on redhat.com or developers.redhat.com. Do not use your social accounts to log in. Then start downloading the Installer from Red Hat Development Suite download page. > > > > If you do not have a Red Hat account, create one at developers.redhat.com. > > ............. > > > > Thanks. > > Robert > > > > [1] https://access.redhat.com/articles/2360571#troubleshooting > > > > > > On 7.?7.?2016 10:32:06, Misha Husnain Ali wrote: > > > >> I remember this issue. Is there any way we can identify the paths leading > >> up to this problem and comprehensively test them to provide clear aid to > >> users who may encounter this issue? I'm happy to volunteer to test some of > >> them if we can identify the various paths users may take. > >> > >> > >> -- > >> Misha Husnain Ali > >> Technical Writer 2, CCS Brisbane > >> > >> On Thu, Jul 7, 2016 at 5:38 AM, Denis Golovin wrote: > >> > >> > T&C's signing workflow is not user friendly ATM. > >> > > >> > Workaround mentioned in https://access.redhat.com/articles/2360571 worked > >> > before for > >> > many dev's who was testing installer. I am going to do check full T&C's > >> > signing again today > >> > and send update ASAP. > >> > > >> > This problem should be affecting only customers who didn't get installer > >> > directly from develper.redhat.com > >> > download. > >> > > >> > Denis > >> > > >> > ----- Original Message ----- > >> > > From: "Robert Kratky" > >> > > To: devtools at redhat.com > >> > > Cc: "Rick Wagner" > >> > > Sent: Wednesday, July 6, 2016 8:51:03 AM > >> > > Subject: Re: [Devtools] Development Suite installation question - C/O > >> > SME with knowledge of installer edits > >> > > > >> > > On 6.?7.?2016 10:08:09, Rick Wagner wrote: > >> > > > >> > > > Hello DevTools, > >> > > > > >> > > > We have a customer case that deals with the error message "Terms and > >> > > > Conditions for the CDK have not been signed". (Actually, this is the > >> > > > second case in 2 days for this problem.) > >> > > > > >> > > > The customer has tried the suggested workaround, without satisfactory > >> > > > results. ("This error appears on the *Log In* page when starting the > >> > > > Installer. To fix the problem, start downloading the Installer to > >> > ensure > >> > > > the *Terms and Conditions* are viewed and accepted and then cancel the > >> > > > binary download." We offer this suggestion in the knowledge article at > >> > > > [1].) > >> > > > > >> > > > Can a knowledgeable SME please offer ideas about alternative courses of > >> > > > action? > >> > > > >> > > Hi Rick, > >> > > > >> > > The problem happens quite often, apparently. I asked about this last > >> > Friday > >> > > in devtools-program [a] -- on behalf of a user who reported the problem > >> > in a > >> > > comment under the old version of the Kbase article [b]. > >> > > > >> > > Any workaround would be appreciated. > >> > > > >> > > Thanks. > >> > > > >> > > Robert > >> > > > >> > > [a] > >> > > > >> > http://post-office.corp.redhat.com/archives/devtools-program/2016-July/msg00001.html > >> > > [b] https://access.redhat.com/articles/2255391#comment-1066361 > >> > > > >> > > > Extra credit: Can you please point me to the source code that produces > >> > > > this edit error? A little spelunking by the Support team sometimes > >> > helps > >> > > > with related issues. > >> > > > > >> > > > Thanks! > >> > > > > >> > > > Rick > >> > > > > >> > > > [1] https://access.redhat.com/articles/2360571 From ccoleman at redhat.com Thu Jul 7 15:09:01 2016 From: ccoleman at redhat.com (Clayton Coleman) Date: Thu, 7 Jul 2016 11:09:01 -0400 Subject: [Devtools] support for OpenShift Container Platform / Origin in minikube? In-Reply-To: References: <34C29FC6-B5F2-439B-95F4-2D42A156E35E@redhat.com> <217D53D0-D256-48E5-8D26-CFD36BF44AC7@redhat.com> <20160706073224.GE96345@nineveh.lan> Message-ID: <9222908504856097678@unknownmsgid> > On Jul 7, 2016, at 4:24 AM, Jimmi Dyson wrote: > > I've started minishift (fork of minikube) at > https://github.com/jimmidyson/minishift if anyone wants to try it out. > Will publish a first release of it later today or tomorrow hopefully. > All feedback welcome - building is pretty simple, as long as you have > the Go toolchain setup. > >> would this be able to run red hat's variation of docker ? > > Of course we can but the question is what benefit it brings? As this > is only for single dev, easy getting started & play what Docker > version is being used should be inconsequential to the ux. The only > problem I can see with using RHT's Docker is the size of the ISO that > minishift will need to download to start the VM. Right now this is > ~36MB & this allows for really speedy startup (effectively no waiting > for download). Switching to RHT's Docker & potentially CentOS/RHEL I > would expect this to grow, which isn't terrible but would affect the > ux somewhat. Not running the Red Hat Docker is a serious problem for OpenShift / Kube, simply given the instability and gaps in upstream Docker. While we're not running production workloads, it's really difficult to certify and fix issues. I have trouble believing we can't match he size of that iso in practical terms. > >> and how about openshift itself ? > > Minishift runs latest version of OpenShift (latest version at time of > build embedded in the minishift binary for speedy start up time) & I > am going to make the version configurable via flags which will > download the specified release from github on startup, with caching > for subsequent runs, etc. > > Thanks, > Jimmi > >> On 6 July 2016 at 08:32, Hardy Ferentschik wrote: >>> On Wed, 06-Jul-2016 00:53, Max Rydahl Andersen wrote: >>> looks great. would this be able to run red hat's variation of docker ? and >>> how about openshift itself ? >> >> My thinking as well. Might be worth investigating. A miniopenshift would have >> a great appeal. >> >> --Hardy > > _______________________________________________ > Devtools mailing list > Devtools at redhat.com > https://www.redhat.com/mailman/listinfo/devtools From rkratky at redhat.com Thu Jul 7 15:33:32 2016 From: rkratky at redhat.com (Robert Kratky) Date: Thu, 07 Jul 2016 17:33:32 +0200 Subject: [Devtools] Development Suite installation question - C/O SME with knowledge of installer edits In-Reply-To: <1829398.oJedtQYAuc@x230> References: <1829398.oJedtQYAuc@x230> Message-ID: <1597469.slTCQpW6SA@x230> Based on a new user comment [1], the "don't use social accounts" workaround doesn't seem to work. It might be related to the fact that he created his RH account on May 18 (i.e. it's not fresh). I asked the user to try a completely new account, but some less drastic solution would be better. Robert [1] https://access.redhat.com/articles/2255391#comment-1069221 On 7.?7.?2016 15:58:06, Robert Kratky wrote: > I updated the text to emphasize that social accounts are not to be used. It now says, basically: > > 1) log in using RH credentials > 2) do not use social accounts > 3) if you can't (i.e. you have no RH account), create a new one > > Robert > > > On 7.?7.?2016 14:42:15, Pete Muir wrote: > > > Robert, as discussed on the call, you might want to recommend a > > "radical" workaround, of just creating a new account entirely, without > > using social media at all. > > > > On 7 July 2016 at 14:38, Robert Kratky wrote: > > > I updated the trouleshooting section in [1] based on the discussion during today's program call. Please, have a look and let me know if what I wrote is accurate -- I cannot test at this moment. > > > > > > This is what it says now: > > > > > > ............. > > > Terms and Conditions Error > > > > > > Error: ?Terms and Conditions for CDK have not been signed? > > > This error appears on the Log In page when starting the Installer. To work around the problem, log in to the Developer Portal using your Red Hat credentials -- the credentials that you created either on redhat.com or developers.redhat.com. Do not use your social accounts to log in. Then start downloading the Installer from Red Hat Development Suite download page. > > > > > > If you do not have a Red Hat account, create one at developers.redhat.com. > > > ............. > > > > > > Thanks. > > > Robert > > > > > > [1] https://access.redhat.com/articles/2360571#troubleshooting > > > > > > > > > On 7.?7.?2016 10:32:06, Misha Husnain Ali wrote: > > > > > >> I remember this issue. Is there any way we can identify the paths leading > > >> up to this problem and comprehensively test them to provide clear aid to > > >> users who may encounter this issue? I'm happy to volunteer to test some of > > >> them if we can identify the various paths users may take. > > >> > > >> > > >> -- > > >> Misha Husnain Ali > > >> Technical Writer 2, CCS Brisbane > > >> > > >> On Thu, Jul 7, 2016 at 5:38 AM, Denis Golovin wrote: > > >> > > >> > T&C's signing workflow is not user friendly ATM. > > >> > > > >> > Workaround mentioned in https://access.redhat.com/articles/2360571 worked > > >> > before for > > >> > many dev's who was testing installer. I am going to do check full T&C's > > >> > signing again today > > >> > and send update ASAP. > > >> > > > >> > This problem should be affecting only customers who didn't get installer > > >> > directly from develper.redhat.com > > >> > download. > > >> > > > >> > Denis > > >> > > > >> > ----- Original Message ----- > > >> > > From: "Robert Kratky" > > >> > > To: devtools at redhat.com > > >> > > Cc: "Rick Wagner" > > >> > > Sent: Wednesday, July 6, 2016 8:51:03 AM > > >> > > Subject: Re: [Devtools] Development Suite installation question - C/O > > >> > SME with knowledge of installer edits > > >> > > > > >> > > On 6.?7.?2016 10:08:09, Rick Wagner wrote: > > >> > > > > >> > > > Hello DevTools, > > >> > > > > > >> > > > We have a customer case that deals with the error message "Terms and > > >> > > > Conditions for the CDK have not been signed". (Actually, this is the > > >> > > > second case in 2 days for this problem.) > > >> > > > > > >> > > > The customer has tried the suggested workaround, without satisfactory > > >> > > > results. ("This error appears on the *Log In* page when starting the > > >> > > > Installer. To fix the problem, start downloading the Installer to > > >> > ensure > > >> > > > the *Terms and Conditions* are viewed and accepted and then cancel the > > >> > > > binary download." We offer this suggestion in the knowledge article at > > >> > > > [1].) > > >> > > > > > >> > > > Can a knowledgeable SME please offer ideas about alternative courses of > > >> > > > action? > > >> > > > > >> > > Hi Rick, > > >> > > > > >> > > The problem happens quite often, apparently. I asked about this last > > >> > Friday > > >> > > in devtools-program [a] -- on behalf of a user who reported the problem > > >> > in a > > >> > > comment under the old version of the Kbase article [b]. > > >> > > > > >> > > Any workaround would be appreciated. > > >> > > > > >> > > Thanks. > > >> > > > > >> > > Robert > > >> > > > > >> > > [a] > > >> > > > > >> > http://post-office.corp.redhat.com/archives/devtools-program/2016-July/msg00001.html > > >> > > [b] https://access.redhat.com/articles/2255391#comment-1066361 > > >> > > > > >> > > > Extra credit: Can you please point me to the source code that produces > > >> > > > this edit error? A little spelunking by the Support team sometimes > > >> > helps > > >> > > > with related issues. > > >> > > > > > >> > > > Thanks! > > >> > > > > > >> > > > Rick > > >> > > > > > >> > > > [1] https://access.redhat.com/articles/2360571 From jdyson at redhat.com Thu Jul 7 15:37:43 2016 From: jdyson at redhat.com (Jimmi Dyson) Date: Thu, 7 Jul 2016 16:37:43 +0100 Subject: [Devtools] support for OpenShift Container Platform / Origin in minikube? In-Reply-To: <9222908504856097678@unknownmsgid> References: <34C29FC6-B5F2-439B-95F4-2D42A156E35E@redhat.com> <217D53D0-D256-48E5-8D26-CFD36BF44AC7@redhat.com> <20160706073224.GE96345@nineveh.lan> <9222908504856097678@unknownmsgid> Message-ID: On 7 July 2016 at 16:09, Clayton Coleman wrote: >> On Jul 7, 2016, at 4:24 AM, Jimmi Dyson wrote: >> >> I've started minishift (fork of minikube) at >> https://github.com/jimmidyson/minishift if anyone wants to try it out. >> Will publish a first release of it later today or tomorrow hopefully. >> All feedback welcome - building is pretty simple, as long as you have >> the Go toolchain setup. >> >>> would this be able to run red hat's variation of docker ? >> >> Of course we can but the question is what benefit it brings? As this >> is only for single dev, easy getting started & play what Docker >> version is being used should be inconsequential to the ux. The only >> problem I can see with using RHT's Docker is the size of the ISO that >> minishift will need to download to start the VM. Right now this is >> ~36MB & this allows for really speedy startup (effectively no waiting >> for download). Switching to RHT's Docker & potentially CentOS/RHEL I >> would expect this to grow, which isn't terrible but would affect the >> ux somewhat. > > Not running the Red Hat Docker is a serious problem for OpenShift / > Kube, simply given the instability and gaps in upstream Docker. While > we're not running production workloads, it's really difficult to > certify and fix issues. If someone can provide me with a URL to a simple tarball of RHT Docker if it's available I'm more than happy to use that in the ISO, but obviously don't want to have to include a full on yum install, etc which will bloat the ISO for little value in this case. > > I have trouble believing we can't match he size of that iso in practical terms. > > >> >>> and how about openshift itself ? >> >> Minishift runs latest version of OpenShift (latest version at time of >> build embedded in the minishift binary for speedy start up time) & I >> am going to make the version configurable via flags which will >> download the specified release from github on startup, with caching >> for subsequent runs, etc. >> >> Thanks, >> Jimmi >> >>> On 6 July 2016 at 08:32, Hardy Ferentschik wrote: >>>> On Wed, 06-Jul-2016 00:53, Max Rydahl Andersen wrote: >>>> looks great. would this be able to run red hat's variation of docker ? and >>>> how about openshift itself ? >>> >>> My thinking as well. Might be worth investigating. A miniopenshift would have >>> a great appeal. >>> >>> --Hardy >> >> _______________________________________________ >> Devtools mailing list >> Devtools at redhat.com >> https://www.redhat.com/mailman/listinfo/devtools From ccoleman at redhat.com Thu Jul 7 16:26:53 2016 From: ccoleman at redhat.com (Clayton Coleman) Date: Thu, 7 Jul 2016 12:26:53 -0400 Subject: [Devtools] support for OpenShift Container Platform / Origin in minikube? In-Reply-To: References: <34C29FC6-B5F2-439B-95F4-2D42A156E35E@redhat.com> <217D53D0-D256-48E5-8D26-CFD36BF44AC7@redhat.com> <20160706073224.GE96345@nineveh.lan> <9222908504856097678@unknownmsgid> Message-ID: The iso for this really belongs to ADB - if this is going to be something we actually promote I'd prefer for the ADB guys to own more of this so we can actually have a chance of this being real, vs a spin off thing that doesn't ultimately go anywhere. As long as the mini bit isn't making too many assumptions about the ISO, this is something we can iterate on. On Thu, Jul 7, 2016 at 11:37 AM, Jimmi Dyson wrote: > On 7 July 2016 at 16:09, Clayton Coleman wrote: > >> On Jul 7, 2016, at 4:24 AM, Jimmi Dyson wrote: > >> > >> I've started minishift (fork of minikube) at > >> https://github.com/jimmidyson/minishift if anyone wants to try it out. > >> Will publish a first release of it later today or tomorrow hopefully. > >> All feedback welcome - building is pretty simple, as long as you have > >> the Go toolchain setup. > >> > >>> would this be able to run red hat's variation of docker ? > >> > >> Of course we can but the question is what benefit it brings? As this > >> is only for single dev, easy getting started & play what Docker > >> version is being used should be inconsequential to the ux. The only > >> problem I can see with using RHT's Docker is the size of the ISO that > >> minishift will need to download to start the VM. Right now this is > >> ~36MB & this allows for really speedy startup (effectively no waiting > >> for download). Switching to RHT's Docker & potentially CentOS/RHEL I > >> would expect this to grow, which isn't terrible but would affect the > >> ux somewhat. > > > > Not running the Red Hat Docker is a serious problem for OpenShift / > > Kube, simply given the instability and gaps in upstream Docker. While > > we're not running production workloads, it's really difficult to > > certify and fix issues. > > If someone can provide me with a URL to a simple tarball of RHT Docker > if it's available I'm more than happy to use that in the ISO, but > obviously don't want to have to include a full on yum install, etc > which will bloat the ISO for little value in this case. > > > > > I have trouble believing we can't match he size of that iso in practical > terms. > > > > > >> > >>> and how about openshift itself ? > >> > >> Minishift runs latest version of OpenShift (latest version at time of > >> build embedded in the minishift binary for speedy start up time) & I > >> am going to make the version configurable via flags which will > >> download the specified release from github on startup, with caching > >> for subsequent runs, etc. > >> > >> Thanks, > >> Jimmi > >> > >>> On 6 July 2016 at 08:32, Hardy Ferentschik > wrote: > >>>> On Wed, 06-Jul-2016 00:53, Max Rydahl Andersen wrote: > >>>> looks great. would this be able to run red hat's variation of docker > ? and > >>>> how about openshift itself ? > >>> > >>> My thinking as well. Might be worth investigating. A miniopenshift > would have > >>> a great appeal. > >>> > >>> --Hardy > >> > >> _______________________________________________ > >> Devtools mailing list > >> Devtools at redhat.com > >> https://www.redhat.com/mailman/listinfo/devtools > -------------- next part -------------- An HTML attachment was scrubbed... URL: From rkratky at redhat.com Thu Jul 7 16:29:32 2016 From: rkratky at redhat.com (Robert Kratky) Date: Thu, 07 Jul 2016 18:29:32 +0200 Subject: [Devtools] Development Suite installation question - C/O SME with knowledge of installer edits In-Reply-To: <1597469.slTCQpW6SA@x230> References: <1829398.oJedtQYAuc@x230> <1597469.slTCQpW6SA@x230> Message-ID: <6413734.nWTzG8j3RH@x230> Follow up: brand new account worked for this user. So: - user didn't use social accounts to log in - orig. account created on dev.rh.com on May 18: doesn't work - new account created on July 7: works Hope this helps a bit. Regards, Robert On 7.?7.?2016 17:33:32, Robert Kratky wrote: > Based on a new user comment [1], the "don't use social accounts" workaround doesn't seem to work. It might be related to the fact that he created his RH account on May 18 (i.e. it's not fresh). > > I asked the user to try a completely new account, but some less drastic solution would be better. > > Robert > > [1] https://access.redhat.com/articles/2255391#comment-1069221 > > > On 7.?7.?2016 15:58:06, Robert Kratky wrote: > > > I updated the text to emphasize that social accounts are not to be used. It now says, basically: > > > > 1) log in using RH credentials > > 2) do not use social accounts > > 3) if you can't (i.e. you have no RH account), create a new one > > > > Robert > > > > > > On 7.?7.?2016 14:42:15, Pete Muir wrote: > > > > > Robert, as discussed on the call, you might want to recommend a > > > "radical" workaround, of just creating a new account entirely, without > > > using social media at all. > > > > > > On 7 July 2016 at 14:38, Robert Kratky wrote: > > > > I updated the trouleshooting section in [1] based on the discussion during today's program call. Please, have a look and let me know if what I wrote is accurate -- I cannot test at this moment. > > > > > > > > This is what it says now: > > > > > > > > ............. > > > > Terms and Conditions Error > > > > > > > > Error: ?Terms and Conditions for CDK have not been signed? > > > > This error appears on the Log In page when starting the Installer. To work around the problem, log in to the Developer Portal using your Red Hat credentials -- the credentials that you created either on redhat.com or developers.redhat.com. Do not use your social accounts to log in. Then start downloading the Installer from Red Hat Development Suite download page. > > > > > > > > If you do not have a Red Hat account, create one at developers.redhat.com. > > > > ............. > > > > > > > > Thanks. > > > > Robert > > > > > > > > [1] https://access.redhat.com/articles/2360571#troubleshooting > > > > > > > > > > > > On 7.?7.?2016 10:32:06, Misha Husnain Ali wrote: > > > > > > > >> I remember this issue. Is there any way we can identify the paths leading > > > >> up to this problem and comprehensively test them to provide clear aid to > > > >> users who may encounter this issue? I'm happy to volunteer to test some of > > > >> them if we can identify the various paths users may take. > > > >> > > > >> > > > >> -- > > > >> Misha Husnain Ali > > > >> Technical Writer 2, CCS Brisbane > > > >> > > > >> On Thu, Jul 7, 2016 at 5:38 AM, Denis Golovin wrote: > > > >> > > > >> > T&C's signing workflow is not user friendly ATM. > > > >> > > > > >> > Workaround mentioned in https://access.redhat.com/articles/2360571 worked > > > >> > before for > > > >> > many dev's who was testing installer. I am going to do check full T&C's > > > >> > signing again today > > > >> > and send update ASAP. > > > >> > > > > >> > This problem should be affecting only customers who didn't get installer > > > >> > directly from develper.redhat.com > > > >> > download. > > > >> > > > > >> > Denis > > > >> > > > > >> > ----- Original Message ----- > > > >> > > From: "Robert Kratky" > > > >> > > To: devtools at redhat.com > > > >> > > Cc: "Rick Wagner" > > > >> > > Sent: Wednesday, July 6, 2016 8:51:03 AM > > > >> > > Subject: Re: [Devtools] Development Suite installation question - C/O > > > >> > SME with knowledge of installer edits > > > >> > > > > > >> > > On 6.?7.?2016 10:08:09, Rick Wagner wrote: > > > >> > > > > > >> > > > Hello DevTools, > > > >> > > > > > > >> > > > We have a customer case that deals with the error message "Terms and > > > >> > > > Conditions for the CDK have not been signed". (Actually, this is the > > > >> > > > second case in 2 days for this problem.) > > > >> > > > > > > >> > > > The customer has tried the suggested workaround, without satisfactory > > > >> > > > results. ("This error appears on the *Log In* page when starting the > > > >> > > > Installer. To fix the problem, start downloading the Installer to > > > >> > ensure > > > >> > > > the *Terms and Conditions* are viewed and accepted and then cancel the > > > >> > > > binary download." We offer this suggestion in the knowledge article at > > > >> > > > [1].) > > > >> > > > > > > >> > > > Can a knowledgeable SME please offer ideas about alternative courses of > > > >> > > > action? > > > >> > > > > > >> > > Hi Rick, > > > >> > > > > > >> > > The problem happens quite often, apparently. I asked about this last > > > >> > Friday > > > >> > > in devtools-program [a] -- on behalf of a user who reported the problem > > > >> > in a > > > >> > > comment under the old version of the Kbase article [b]. > > > >> > > > > > >> > > Any workaround would be appreciated. > > > >> > > > > > >> > > Thanks. > > > >> > > > > > >> > > Robert > > > >> > > > > > >> > > [a] > > > >> > > > > > >> > http://post-office.corp.redhat.com/archives/devtools-program/2016-July/msg00001.html > > > >> > > [b] https://access.redhat.com/articles/2255391#comment-1066361 > > > >> > > > > > >> > > > Extra credit: Can you please point me to the source code that produces > > > >> > > > this edit error? A little spelunking by the Support team sometimes > > > >> > helps > > > >> > > > with related issues. > > > >> > > > > > > >> > > > Thanks! > > > >> > > > > > > >> > > > Rick > > > >> > > > > > > >> > > > [1] https://access.redhat.com/articles/2360571 From pmuir at redhat.com Thu Jul 7 16:36:38 2016 From: pmuir at redhat.com (Pete Muir) Date: Thu, 7 Jul 2016 17:36:38 +0100 Subject: [Devtools] support for OpenShift Container Platform / Origin in minikube? In-Reply-To: References: <34C29FC6-B5F2-439B-95F4-2D42A156E35E@redhat.com> <217D53D0-D256-48E5-8D26-CFD36BF44AC7@redhat.com> <20160706073224.GE96345@nineveh.lan> <9222908504856097678@unknownmsgid> Message-ID: Hardy, Lala and the rest of the ADB team are going to investigate this over the next few weeks (whether we can replace the ADB infra with minishift). For the product version it must be based on something that we productise (which currently is RHEL or Atomic AFAIK) - doing it on top of something like Alpine is not an option. I would also worry about having a radically different upstream from the product version, as I think this can cause bugs, but I'll leave this one to the team to figure out :-) I've also asked Ian a few times if we can try to build smaller images - something to keep trying for ;-) On 7 July 2016 at 17:26, Clayton Coleman wrote: > The iso for this really belongs to ADB - if this is going to be something we > actually promote I'd prefer for the ADB guys to own more of this so we can > actually have a chance of this being real, vs a spin off thing that doesn't > ultimately go anywhere. > > As long as the mini bit isn't making too many assumptions about the ISO, > this is something we can iterate on. > > On Thu, Jul 7, 2016 at 11:37 AM, Jimmi Dyson wrote: >> >> On 7 July 2016 at 16:09, Clayton Coleman wrote: >> >> On Jul 7, 2016, at 4:24 AM, Jimmi Dyson wrote: >> >> >> >> I've started minishift (fork of minikube) at >> >> https://github.com/jimmidyson/minishift if anyone wants to try it out. >> >> Will publish a first release of it later today or tomorrow hopefully. >> >> All feedback welcome - building is pretty simple, as long as you have >> >> the Go toolchain setup. >> >> >> >>> would this be able to run red hat's variation of docker ? >> >> >> >> Of course we can but the question is what benefit it brings? As this >> >> is only for single dev, easy getting started & play what Docker >> >> version is being used should be inconsequential to the ux. The only >> >> problem I can see with using RHT's Docker is the size of the ISO that >> >> minishift will need to download to start the VM. Right now this is >> >> ~36MB & this allows for really speedy startup (effectively no waiting >> >> for download). Switching to RHT's Docker & potentially CentOS/RHEL I >> >> would expect this to grow, which isn't terrible but would affect the >> >> ux somewhat. >> > >> > Not running the Red Hat Docker is a serious problem for OpenShift / >> > Kube, simply given the instability and gaps in upstream Docker. While >> > we're not running production workloads, it's really difficult to >> > certify and fix issues. >> >> If someone can provide me with a URL to a simple tarball of RHT Docker >> if it's available I'm more than happy to use that in the ISO, but >> obviously don't want to have to include a full on yum install, etc >> which will bloat the ISO for little value in this case. >> >> > >> > I have trouble believing we can't match he size of that iso in practical >> > terms. >> > >> > >> >> >> >>> and how about openshift itself ? >> >> >> >> Minishift runs latest version of OpenShift (latest version at time of >> >> build embedded in the minishift binary for speedy start up time) & I >> >> am going to make the version configurable via flags which will >> >> download the specified release from github on startup, with caching >> >> for subsequent runs, etc. >> >> >> >> Thanks, >> >> Jimmi >> >> >> >>> On 6 July 2016 at 08:32, Hardy Ferentschik >> >>> wrote: >> >>>> On Wed, 06-Jul-2016 00:53, Max Rydahl Andersen wrote: >> >>>> looks great. would this be able to run red hat's variation of docker >> >>>> ? and >> >>>> how about openshift itself ? >> >>> >> >>> My thinking as well. Might be worth investigating. A miniopenshift >> >>> would have >> >>> a great appeal. >> >>> >> >>> --Hardy >> >> >> >> _______________________________________________ >> >> 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 > From pmuir at redhat.com Thu Jul 7 16:40:36 2016 From: pmuir at redhat.com (Pete Muir) Date: Thu, 7 Jul 2016 17:40:36 +0100 Subject: [Devtools] Development Suite installation question - C/O SME with knowledge of installer edits In-Reply-To: <6413734.nWTzG8j3RH@x230> References: <1829398.oJedtQYAuc@x230> <1597469.slTCQpW6SA@x230> <6413734.nWTzG8j3RH@x230> Message-ID: Very helpful Robert, as it helps us identify that there is a problem on the server side around older accounts that somehow aren't being properly upgraded. Mark/David, can you treat this as an urgent issue to look in to, as it's getting reported by customers. Rick Wagner is getting more info from customers, but Robert seems to have identified at least one failing path. On 7 July 2016 at 17:29, Robert Kratky wrote: > Follow up: brand new account worked for this user. So: > > - user didn't use social accounts to log in > - orig. account created on dev.rh.com on May 18: doesn't work > - new account created on July 7: works > > Hope this helps a bit. > > Regards, > Robert > > > On 7.?7.?2016 17:33:32, Robert Kratky wrote: > >> Based on a new user comment [1], the "don't use social accounts" workaround doesn't seem to work. It might be related to the fact that he created his RH account on May 18 (i.e. it's not fresh). >> >> I asked the user to try a completely new account, but some less drastic solution would be better. >> >> Robert >> >> [1] https://access.redhat.com/articles/2255391#comment-1069221 >> >> >> On 7.?7.?2016 15:58:06, Robert Kratky wrote: >> >> > I updated the text to emphasize that social accounts are not to be used. It now says, basically: >> > >> > 1) log in using RH credentials >> > 2) do not use social accounts >> > 3) if you can't (i.e. you have no RH account), create a new one >> > >> > Robert >> > >> > >> > On 7.?7.?2016 14:42:15, Pete Muir wrote: >> > >> > > Robert, as discussed on the call, you might want to recommend a >> > > "radical" workaround, of just creating a new account entirely, without >> > > using social media at all. >> > > >> > > On 7 July 2016 at 14:38, Robert Kratky wrote: >> > > > I updated the trouleshooting section in [1] based on the discussion during today's program call. Please, have a look and let me know if what I wrote is accurate -- I cannot test at this moment. >> > > > >> > > > This is what it says now: >> > > > >> > > > ............. >> > > > Terms and Conditions Error >> > > > >> > > > Error: ?Terms and Conditions for CDK have not been signed? >> > > > This error appears on the Log In page when starting the Installer. To work around the problem, log in to the Developer Portal using your Red Hat credentials -- the credentials that you created either on redhat.com or developers.redhat.com. Do not use your social accounts to log in. Then start downloading the Installer from Red Hat Development Suite download page. >> > > > >> > > > If you do not have a Red Hat account, create one at developers.redhat.com. >> > > > ............. >> > > > >> > > > Thanks. >> > > > Robert >> > > > >> > > > [1] https://access.redhat.com/articles/2360571#troubleshooting >> > > > >> > > > >> > > > On 7.?7.?2016 10:32:06, Misha Husnain Ali wrote: >> > > > >> > > >> I remember this issue. Is there any way we can identify the paths leading >> > > >> up to this problem and comprehensively test them to provide clear aid to >> > > >> users who may encounter this issue? I'm happy to volunteer to test some of >> > > >> them if we can identify the various paths users may take. >> > > >> >> > > >> >> > > >> -- >> > > >> Misha Husnain Ali >> > > >> Technical Writer 2, CCS Brisbane >> > > >> >> > > >> On Thu, Jul 7, 2016 at 5:38 AM, Denis Golovin wrote: >> > > >> >> > > >> > T&C's signing workflow is not user friendly ATM. >> > > >> > >> > > >> > Workaround mentioned in https://access.redhat.com/articles/2360571 worked >> > > >> > before for >> > > >> > many dev's who was testing installer. I am going to do check full T&C's >> > > >> > signing again today >> > > >> > and send update ASAP. >> > > >> > >> > > >> > This problem should be affecting only customers who didn't get installer >> > > >> > directly from develper.redhat.com >> > > >> > download. >> > > >> > >> > > >> > Denis >> > > >> > >> > > >> > ----- Original Message ----- >> > > >> > > From: "Robert Kratky" >> > > >> > > To: devtools at redhat.com >> > > >> > > Cc: "Rick Wagner" >> > > >> > > Sent: Wednesday, July 6, 2016 8:51:03 AM >> > > >> > > Subject: Re: [Devtools] Development Suite installation question - C/O >> > > >> > SME with knowledge of installer edits >> > > >> > > >> > > >> > > On 6.?7.?2016 10:08:09, Rick Wagner wrote: >> > > >> > > >> > > >> > > > Hello DevTools, >> > > >> > > > >> > > >> > > > We have a customer case that deals with the error message "Terms and >> > > >> > > > Conditions for the CDK have not been signed". (Actually, this is the >> > > >> > > > second case in 2 days for this problem.) >> > > >> > > > >> > > >> > > > The customer has tried the suggested workaround, without satisfactory >> > > >> > > > results. ("This error appears on the *Log In* page when starting the >> > > >> > > > Installer. To fix the problem, start downloading the Installer to >> > > >> > ensure >> > > >> > > > the *Terms and Conditions* are viewed and accepted and then cancel the >> > > >> > > > binary download." We offer this suggestion in the knowledge article at >> > > >> > > > [1].) >> > > >> > > > >> > > >> > > > Can a knowledgeable SME please offer ideas about alternative courses of >> > > >> > > > action? >> > > >> > > >> > > >> > > Hi Rick, >> > > >> > > >> > > >> > > The problem happens quite often, apparently. I asked about this last >> > > >> > Friday >> > > >> > > in devtools-program [a] -- on behalf of a user who reported the problem >> > > >> > in a >> > > >> > > comment under the old version of the Kbase article [b]. >> > > >> > > >> > > >> > > Any workaround would be appreciated. >> > > >> > > >> > > >> > > Thanks. >> > > >> > > >> > > >> > > Robert >> > > >> > > >> > > >> > > [a] >> > > >> > > >> > > >> > http://post-office.corp.redhat.com/archives/devtools-program/2016-July/msg00001.html >> > > >> > > [b] https://access.redhat.com/articles/2255391#comment-1066361 >> > > >> > > >> > > >> > > > Extra credit: Can you please point me to the source code that produces >> > > >> > > > this edit error? A little spelunking by the Support team sometimes >> > > >> > helps >> > > >> > > > with related issues. >> > > >> > > > >> > > >> > > > Thanks! >> > > >> > > > >> > > >> > > > Rick >> > > >> > > > >> > > >> > > > [1] https://access.redhat.com/articles/2360571 > > > _______________________________________________ > Devtools mailing list > Devtools at redhat.com > https://www.redhat.com/mailman/listinfo/devtools From jdyson at redhat.com Thu Jul 7 16:48:02 2016 From: jdyson at redhat.com (Jimmi Dyson) Date: Thu, 7 Jul 2016 17:48:02 +0100 Subject: [Devtools] support for OpenShift Container Platform / Origin in minikube? In-Reply-To: References: <34C29FC6-B5F2-439B-95F4-2D42A156E35E@redhat.com> <217D53D0-D256-48E5-8D26-CFD36BF44AC7@redhat.com> <20160706073224.GE96345@nineveh.lan> <9222908504856097678@unknownmsgid> Message-ID: On 7 July 2016 at 17:36, Pete Muir wrote: > Hardy, Lala and the rest of the ADB team are going to investigate this > over the next few weeks (whether we can replace the ADB infra with > minishift). > > For the product version it must be based on something that we > productise (which currently is RHEL or Atomic AFAIK) - doing it on top > of something like Alpine is not an option. You can see what it's built from at https://hub.docker.com/r/boot2docker/boot2docker/~/dockerfile/ . Don't worry about the FROM debian:jessie - that's just to create the builder image. You can see the minimal stuff it's actually installing in the final ISO. > > I would also worry about having a radically different upstream from > the product version, as I think this can cause bugs, but I'll leave > this one to the team to figure out :-) > > I've also asked Ian a few times if we can try to build smaller images > - something to keep trying for ;-) I don't see why we couldn't have the equivalent of boot2docker.iso image that minikube uses: basically a kernel & docker.... that's it. Sure we can use a RHEL/CentOS kernel, right? Just please not the whole RHEL install ;) > > On 7 July 2016 at 17:26, Clayton Coleman wrote: >> The iso for this really belongs to ADB - if this is going to be something we >> actually promote I'd prefer for the ADB guys to own more of this so we can >> actually have a chance of this being real, vs a spin off thing that doesn't >> ultimately go anywhere. >> >> As long as the mini bit isn't making too many assumptions about the ISO, >> this is something we can iterate on. >> >> On Thu, Jul 7, 2016 at 11:37 AM, Jimmi Dyson wrote: >>> >>> On 7 July 2016 at 16:09, Clayton Coleman wrote: >>> >> On Jul 7, 2016, at 4:24 AM, Jimmi Dyson wrote: >>> >> >>> >> I've started minishift (fork of minikube) at >>> >> https://github.com/jimmidyson/minishift if anyone wants to try it out. >>> >> Will publish a first release of it later today or tomorrow hopefully. >>> >> All feedback welcome - building is pretty simple, as long as you have >>> >> the Go toolchain setup. >>> >> >>> >>> would this be able to run red hat's variation of docker ? >>> >> >>> >> Of course we can but the question is what benefit it brings? As this >>> >> is only for single dev, easy getting started & play what Docker >>> >> version is being used should be inconsequential to the ux. The only >>> >> problem I can see with using RHT's Docker is the size of the ISO that >>> >> minishift will need to download to start the VM. Right now this is >>> >> ~36MB & this allows for really speedy startup (effectively no waiting >>> >> for download). Switching to RHT's Docker & potentially CentOS/RHEL I >>> >> would expect this to grow, which isn't terrible but would affect the >>> >> ux somewhat. >>> > >>> > Not running the Red Hat Docker is a serious problem for OpenShift / >>> > Kube, simply given the instability and gaps in upstream Docker. While >>> > we're not running production workloads, it's really difficult to >>> > certify and fix issues. >>> >>> If someone can provide me with a URL to a simple tarball of RHT Docker >>> if it's available I'm more than happy to use that in the ISO, but >>> obviously don't want to have to include a full on yum install, etc >>> which will bloat the ISO for little value in this case. >>> >>> > >>> > I have trouble believing we can't match he size of that iso in practical >>> > terms. >>> > >>> > >>> >> >>> >>> and how about openshift itself ? >>> >> >>> >> Minishift runs latest version of OpenShift (latest version at time of >>> >> build embedded in the minishift binary for speedy start up time) & I >>> >> am going to make the version configurable via flags which will >>> >> download the specified release from github on startup, with caching >>> >> for subsequent runs, etc. >>> >> >>> >> Thanks, >>> >> Jimmi >>> >> >>> >>> On 6 July 2016 at 08:32, Hardy Ferentschik >>> >>> wrote: >>> >>>> On Wed, 06-Jul-2016 00:53, Max Rydahl Andersen wrote: >>> >>>> looks great. would this be able to run red hat's variation of docker >>> >>>> ? and >>> >>>> how about openshift itself ? >>> >>> >>> >>> My thinking as well. Might be worth investigating. A miniopenshift >>> >>> would have >>> >>> a great appeal. >>> >>> >>> >>> --Hardy >>> >> >>> >> _______________________________________________ >>> >> 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 >> From ccoleman at redhat.com Thu Jul 7 16:55:42 2016 From: ccoleman at redhat.com (Clayton Coleman) Date: Thu, 7 Jul 2016 12:55:42 -0400 Subject: [Devtools] support for OpenShift Container Platform / Origin in minikube? In-Reply-To: References: <34C29FC6-B5F2-439B-95F4-2D42A156E35E@redhat.com> <217D53D0-D256-48E5-8D26-CFD36BF44AC7@redhat.com> <20160706073224.GE96345@nineveh.lan> <9222908504856097678@unknownmsgid> Message-ID: On Thu, Jul 7, 2016 at 12:48 PM, Jimmi Dyson wrote: > On 7 July 2016 at 17:36, Pete Muir wrote: > > Hardy, Lala and the rest of the ADB team are going to investigate this > > over the next few weeks (whether we can replace the ADB infra with > > minishift). > > > > For the product version it must be based on something that we > > productise (which currently is RHEL or Atomic AFAIK) - doing it on top > > of something like Alpine is not an option. > > You can see what it's built from at > https://hub.docker.com/r/boot2docker/boot2docker/~/dockerfile/ . Don't > worry about the FROM debian:jessie - that's just to create the builder > image. You can see the minimal stuff it's actually installing in the > final ISO. > > > > > I would also worry about having a radically different upstream from > > the product version, as I think this can cause bugs, but I'll leave > > this one to the team to figure out :-) > > > > I've also asked Ian a few times if we can try to build smaller images > > - something to keep trying for ;-) > > I don't see why we couldn't have the equivalent of boot2docker.iso > image that minikube uses: basically a kernel & docker.... that's it. > Sure we can use a RHEL/CentOS kernel, right? Just please not the whole > RHEL install ;) Agreed. I think Pete and I are just saying that we need to make an effort to fix the actual problem (we don't have a small ISO for RHEL/CentOS that represents our strengths in containers), and that we should also be taking those steps in parallel. -------------- next part -------------- An HTML attachment was scrubbed... URL: From pmuir at redhat.com Thu Jul 7 17:07:18 2016 From: pmuir at redhat.com (Pete Muir) Date: Thu, 7 Jul 2016 18:07:18 +0100 Subject: [Devtools] support for OpenShift Container Platform / Origin in minikube? In-Reply-To: References: <34C29FC6-B5F2-439B-95F4-2D42A156E35E@redhat.com> <217D53D0-D256-48E5-8D26-CFD36BF44AC7@redhat.com> <20160706073224.GE96345@nineveh.lan> <9222908504856097678@unknownmsgid> Message-ID: On 7 July 2016 at 17:55, Clayton Coleman wrote: > > > On Thu, Jul 7, 2016 at 12:48 PM, Jimmi Dyson wrote: >> >> On 7 July 2016 at 17:36, Pete Muir wrote: >> > Hardy, Lala and the rest of the ADB team are going to investigate this >> > over the next few weeks (whether we can replace the ADB infra with >> > minishift). >> > >> > For the product version it must be based on something that we >> > productise (which currently is RHEL or Atomic AFAIK) - doing it on top >> > of something like Alpine is not an option. >> >> You can see what it's built from at >> https://hub.docker.com/r/boot2docker/boot2docker/~/dockerfile/ . Don't >> worry about the FROM debian:jessie - that's just to create the builder >> image. You can see the minimal stuff it's actually installing in the >> final ISO. >> >> > >> > I would also worry about having a radically different upstream from >> > the product version, as I think this can cause bugs, but I'll leave >> > this one to the team to figure out :-) >> > >> > I've also asked Ian a few times if we can try to build smaller images >> > - something to keep trying for ;-) >> >> I don't see why we couldn't have the equivalent of boot2docker.iso >> image that minikube uses: basically a kernel & docker.... that's it. >> Sure we can use a RHEL/CentOS kernel, right? Just please not the whole >> RHEL install ;) > > > Agreed. I think Pete and I are just saying that we need to make an effort > to fix the actual problem (we don't have a small ISO for RHEL/CentOS that > represents our strengths in containers), and that we should also be taking > those steps in parallel. Exactly. I also still don't understand why we don't ship Atomic Host as the default OS in the container runtime portion of the CDK - this seems like an obvious thing to do . From lmohanty at redhat.com Thu Jul 7 18:21:40 2016 From: lmohanty at redhat.com (Lalatendu Mohanty) Date: Thu, 7 Jul 2016 23:51:40 +0530 Subject: [Devtools] support for OpenShift Container Platform / Origin in minikube? In-Reply-To: <20160707093014.GC6387@nineveh.lan> References: <34C29FC6-B5F2-439B-95F4-2D42A156E35E@redhat.com> <217D53D0-D256-48E5-8D26-CFD36BF44AC7@redhat.com> <20160706073224.GE96345@nineveh.lan> <519c466c-c4d8-3880-2d1e-4078ef43e697@redhat.com> <20160707093014.GC6387@nineveh.lan> Message-ID: <027fb9dc-f580-e8d0-2e83-f7662efd1cc6@redhat.com> On 07/07/2016 03:00 PM, Hardy Ferentschik wrote: > Hi, > > On Thu, 07-Jul-2016 10:38, Roland Huss wrote: >> I had the luck to try it out first and I have to say, it's awesome. From >> scratch to a running OpenShift origin with minishift it took me 1:56 min >> (11 MBit/s downstream) for the initial run and 30s for subsequent starts. > That is absolutely amazing. I cannot wait to try the release once it is out. > >> On OS X it uses xhyve under the covers so not even VirtualBox is >> required (an no local Docker installation, btw). > :-) > >> Kudos Jimmi, it's really extraordinary ! > So where does this leave us with ADB? If minishift gets traction I have a hard > time seeing people wanting to use ADB. > > --Hardy > ADB should be the upstream project for what ever we deliver with CDK. If we are changing underlying bits for CDK then ADB should adapt to it. -Lala > > > _______________________________________________ > Devtools mailing list > Devtools at redhat.com > https://www.redhat.com/mailman/listinfo/devtools -------------- next part -------------- An HTML attachment was scrubbed... URL: From rwagner at redhat.com Thu Jul 7 18:08:54 2016 From: rwagner at redhat.com (Rick Wagner) Date: Thu, 7 Jul 2016 13:08:54 -0500 Subject: [Devtools] Development Suite installation question - C/O SME with knowledge of installer edits In-Reply-To: References: <1829398.oJedtQYAuc@x230> <1597469.slTCQpW6SA@x230> <6413734.nWTzG8j3RH@x230> Message-ID: Hello All, Additional information, this from (no SalesForce acct required) the support case at [1]. The customer is telling us the 'use a new account' workaround was successful with a Windows 10 machine. A second attempt on a Win 7 machine fails. The failed effort: - Is using the userid 'ryanbuckett' - Previously failed effort (the original account) was 'SumaGeethakumari'. The customer is asking if the downloaded exectuable must be used on the machine it was downloaded to? (If the username specified for download and installation are the same, is it relevant where the artifact was downloaded to?) Thanks, Rick [1] https://access.redhat.com/support/cases/01662411 On Thu, Jul 7, 2016 at 11:40 AM, Pete Muir wrote: > Very helpful Robert, as it helps us identify that there is a problem > on the server side around older accounts that somehow aren't being > properly upgraded. > > Mark/David, can you treat this as an urgent issue to look in to, as > it's getting reported by customers. > > Rick Wagner is getting more info from customers, but Robert seems to > have identified at least one failing path. > > On 7 July 2016 at 17:29, Robert Kratky wrote: > > Follow up: brand new account worked for this user. So: > > > > - user didn't use social accounts to log in > > - orig. account created on dev.rh.com on May 18: doesn't work > > - new account created on July 7: works > > > > Hope this helps a bit. > > > > Regards, > > Robert > > > > > > On 7.?7.?2016 17:33:32, Robert Kratky wrote: > > > >> Based on a new user comment [1], the "don't use social accounts" > workaround doesn't seem to work. It might be related to the fact that he > created his RH account on May 18 (i.e. it's not fresh). > >> > >> I asked the user to try a completely new account, but some less drastic > solution would be better. > >> > >> Robert > >> > >> [1] https://access.redhat.com/articles/2255391#comment-1069221 > >> > >> > >> On 7.?7.?2016 15:58:06, Robert Kratky wrote: > >> > >> > I updated the text to emphasize that social accounts are not to be > used. It now says, basically: > >> > > >> > 1) log in using RH credentials > >> > 2) do not use social accounts > >> > 3) if you can't (i.e. you have no RH account), create a new one > >> > > >> > Robert > >> > > >> > > >> > On 7.?7.?2016 14:42:15, Pete Muir wrote: > >> > > >> > > Robert, as discussed on the call, you might want to recommend a > >> > > "radical" workaround, of just creating a new account entirely, > without > >> > > using social media at all. > >> > > > >> > > On 7 July 2016 at 14:38, Robert Kratky wrote: > >> > > > I updated the trouleshooting section in [1] based on the > discussion during today's program call. Please, have a look and let me know > if what I wrote is accurate -- I cannot test at this moment. > >> > > > > >> > > > This is what it says now: > >> > > > > >> > > > ............. > >> > > > Terms and Conditions Error > >> > > > > >> > > > Error: ?Terms and Conditions for CDK have not been signed? > >> > > > This error appears on the Log In page when starting the > Installer. To work around the problem, log in to the Developer Portal using > your Red Hat credentials -- the credentials that you created either on > redhat.com or developers.redhat.com. Do not use your social accounts to > log in. Then start downloading the Installer from Red Hat Development Suite > download page. > >> > > > > >> > > > If you do not have a Red Hat account, create one at > developers.redhat.com. > >> > > > ............. > >> > > > > >> > > > Thanks. > >> > > > Robert > >> > > > > >> > > > [1] https://access.redhat.com/articles/2360571#troubleshooting > >> > > > > >> > > > > >> > > > On 7.?7.?2016 10:32:06, Misha Husnain Ali wrote: > >> > > > > >> > > >> I remember this issue. Is there any way we can identify the > paths leading > >> > > >> up to this problem and comprehensively test them to provide > clear aid to > >> > > >> users who may encounter this issue? I'm happy to volunteer to > test some of > >> > > >> them if we can identify the various paths users may take. > >> > > >> > >> > > >> > >> > > >> -- > >> > > >> Misha Husnain Ali > >> > > >> Technical Writer 2, CCS Brisbane > >> > > >> > >> > > >> On Thu, Jul 7, 2016 at 5:38 AM, Denis Golovin < > degolovi at redhat.com> wrote: > >> > > >> > >> > > >> > T&C's signing workflow is not user friendly ATM. > >> > > >> > > >> > > >> > Workaround mentioned in > https://access.redhat.com/articles/2360571 worked > >> > > >> > before for > >> > > >> > many dev's who was testing installer. I am going to do check > full T&C's > >> > > >> > signing again today > >> > > >> > and send update ASAP. > >> > > >> > > >> > > >> > This problem should be affecting only customers who didn't get > installer > >> > > >> > directly from develper.redhat.com > >> > > >> > download. > >> > > >> > > >> > > >> > Denis > >> > > >> > > >> > > >> > ----- Original Message ----- > >> > > >> > > From: "Robert Kratky" > >> > > >> > > To: devtools at redhat.com > >> > > >> > > Cc: "Rick Wagner" > >> > > >> > > Sent: Wednesday, July 6, 2016 8:51:03 AM > >> > > >> > > Subject: Re: [Devtools] Development Suite installation > question - C/O > >> > > >> > SME with knowledge of installer edits > >> > > >> > > > >> > > >> > > On 6.?7.?2016 10:08:09, Rick Wagner wrote: > >> > > >> > > > >> > > >> > > > Hello DevTools, > >> > > >> > > > > >> > > >> > > > We have a customer case that deals with the error message > "Terms and > >> > > >> > > > Conditions for the CDK have not been signed". (Actually, > this is the > >> > > >> > > > second case in 2 days for this problem.) > >> > > >> > > > > >> > > >> > > > The customer has tried the suggested workaround, without > satisfactory > >> > > >> > > > results. ("This error appears on the *Log In* page when > starting the > >> > > >> > > > Installer. To fix the problem, start downloading the > Installer to > >> > > >> > ensure > >> > > >> > > > the *Terms and Conditions* are viewed and accepted and > then cancel the > >> > > >> > > > binary download." We offer this suggestion in the > knowledge article at > >> > > >> > > > [1].) > >> > > >> > > > > >> > > >> > > > Can a knowledgeable SME please offer ideas about > alternative courses of > >> > > >> > > > action? > >> > > >> > > > >> > > >> > > Hi Rick, > >> > > >> > > > >> > > >> > > The problem happens quite often, apparently. I asked about > this last > >> > > >> > Friday > >> > > >> > > in devtools-program [a] -- on behalf of a user who reported > the problem > >> > > >> > in a > >> > > >> > > comment under the old version of the Kbase article [b]. > >> > > >> > > > >> > > >> > > Any workaround would be appreciated. > >> > > >> > > > >> > > >> > > Thanks. > >> > > >> > > > >> > > >> > > Robert > >> > > >> > > > >> > > >> > > [a] > >> > > >> > > > >> > > >> > > http://post-office.corp.redhat.com/archives/devtools-program/2016-July/msg00001.html > >> > > >> > > [b] > https://access.redhat.com/articles/2255391#comment-1066361 > >> > > >> > > > >> > > >> > > > Extra credit: Can you please point me to the source code > that produces > >> > > >> > > > this edit error? A little spelunking by the Support team > sometimes > >> > > >> > helps > >> > > >> > > > with related issues. > >> > > >> > > > > >> > > >> > > > Thanks! > >> > > >> > > > > >> > > >> > > > Rick > >> > > >> > > > > >> > > >> > > > [1] https://access.redhat.com/articles/2360571 > > > > > > _______________________________________________ > > Devtools mailing list > > Devtools at redhat.com > > https://www.redhat.com/mailman/listinfo/devtools > -------------- next part -------------- An HTML attachment was scrubbed... URL: From pmuir at redhat.com Thu Jul 7 18:34:47 2016 From: pmuir at redhat.com (Pete Muir) Date: Thu, 7 Jul 2016 19:34:47 +0100 Subject: [Devtools] Development Suite installation question - C/O SME with knowledge of installer edits In-Reply-To: References: <1829398.oJedtQYAuc@x230> <1597469.slTCQpW6SA@x230> <6413734.nWTzG8j3RH@x230> Message-ID: On 7 July 2016 at 19:08, Rick Wagner wrote: > Hello All, > > Additional information, this from (no SalesForce acct required) the support > case at [1]. > > The customer is telling us the 'use a new account' workaround was successful > with a Windows 10 machine. A second attempt on a Win 7 machine fails. > > The failed effort: > - Is using the userid 'ryanbuckett' > - Previously failed effort (the original account) was 'SumaGeethakumari'. > > The customer is asking if the downloaded exectuable must be used on the > machine it was downloaded to? (If the username specified for download and > installation are the same, is it relevant where the artifact was downloaded > to?) No, the link is usernames. You must use the username you downloaded with when you run the installer. David/Mark, can you check these user accounts - have they signed the RHEL Developer Suite T&C? > > Thanks, > > Rick > > [1] https://access.redhat.com/support/cases/01662411 > > On Thu, Jul 7, 2016 at 11:40 AM, Pete Muir wrote: >> >> Very helpful Robert, as it helps us identify that there is a problem >> on the server side around older accounts that somehow aren't being >> properly upgraded. >> >> Mark/David, can you treat this as an urgent issue to look in to, as >> it's getting reported by customers. >> >> Rick Wagner is getting more info from customers, but Robert seems to >> have identified at least one failing path. >> >> On 7 July 2016 at 17:29, Robert Kratky wrote: >> > Follow up: brand new account worked for this user. So: >> > >> > - user didn't use social accounts to log in >> > - orig. account created on dev.rh.com on May 18: doesn't work >> > - new account created on July 7: works >> > >> > Hope this helps a bit. >> > >> > Regards, >> > Robert >> > >> > >> > On 7.?7.?2016 17:33:32, Robert Kratky wrote: >> > >> >> Based on a new user comment [1], the "don't use social accounts" >> >> workaround doesn't seem to work. It might be related to the fact that he >> >> created his RH account on May 18 (i.e. it's not fresh). >> >> >> >> I asked the user to try a completely new account, but some less drastic >> >> solution would be better. >> >> >> >> Robert >> >> >> >> [1] https://access.redhat.com/articles/2255391#comment-1069221 >> >> >> >> >> >> On 7.?7.?2016 15:58:06, Robert Kratky wrote: >> >> >> >> > I updated the text to emphasize that social accounts are not to be >> >> > used. It now says, basically: >> >> > >> >> > 1) log in using RH credentials >> >> > 2) do not use social accounts >> >> > 3) if you can't (i.e. you have no RH account), create a new one >> >> > >> >> > Robert >> >> > >> >> > >> >> > On 7.?7.?2016 14:42:15, Pete Muir wrote: >> >> > >> >> > > Robert, as discussed on the call, you might want to recommend a >> >> > > "radical" workaround, of just creating a new account entirely, >> >> > > without >> >> > > using social media at all. >> >> > > >> >> > > On 7 July 2016 at 14:38, Robert Kratky wrote: >> >> > > > I updated the trouleshooting section in [1] based on the >> >> > > > discussion during today's program call. Please, have a look and let me know >> >> > > > if what I wrote is accurate -- I cannot test at this moment. >> >> > > > >> >> > > > This is what it says now: >> >> > > > >> >> > > > ............. >> >> > > > Terms and Conditions Error >> >> > > > >> >> > > > Error: ?Terms and Conditions for CDK have not been signed? >> >> > > > This error appears on the Log In page when starting the >> >> > > > Installer. To work around the problem, log in to the Developer Portal using >> >> > > > your Red Hat credentials -- the credentials that you created either on >> >> > > > redhat.com or developers.redhat.com. Do not use your social accounts to log >> >> > > > in. Then start downloading the Installer from Red Hat Development Suite >> >> > > > download page. >> >> > > > >> >> > > > If you do not have a Red Hat account, create one at >> >> > > > developers.redhat.com. >> >> > > > ............. >> >> > > > >> >> > > > Thanks. >> >> > > > Robert >> >> > > > >> >> > > > [1] https://access.redhat.com/articles/2360571#troubleshooting >> >> > > > >> >> > > > >> >> > > > On 7.?7.?2016 10:32:06, Misha Husnain Ali wrote: >> >> > > > >> >> > > >> I remember this issue. Is there any way we can identify the >> >> > > >> paths leading >> >> > > >> up to this problem and comprehensively test them to provide >> >> > > >> clear aid to >> >> > > >> users who may encounter this issue? I'm happy to volunteer to >> >> > > >> test some of >> >> > > >> them if we can identify the various paths users may take. >> >> > > >> >> >> > > >> >> >> > > >> -- >> >> > > >> Misha Husnain Ali >> >> > > >> Technical Writer 2, CCS Brisbane >> >> > > >> >> >> > > >> On Thu, Jul 7, 2016 at 5:38 AM, Denis Golovin >> >> > > >> wrote: >> >> > > >> >> >> > > >> > T&C's signing workflow is not user friendly ATM. >> >> > > >> > >> >> > > >> > Workaround mentioned in >> >> > > >> > https://access.redhat.com/articles/2360571 worked >> >> > > >> > before for >> >> > > >> > many dev's who was testing installer. I am going to do check >> >> > > >> > full T&C's >> >> > > >> > signing again today >> >> > > >> > and send update ASAP. >> >> > > >> > >> >> > > >> > This problem should be affecting only customers who didn't get >> >> > > >> > installer >> >> > > >> > directly from develper.redhat.com >> >> > > >> > download. >> >> > > >> > >> >> > > >> > Denis >> >> > > >> > >> >> > > >> > ----- Original Message ----- >> >> > > >> > > From: "Robert Kratky" >> >> > > >> > > To: devtools at redhat.com >> >> > > >> > > Cc: "Rick Wagner" >> >> > > >> > > Sent: Wednesday, July 6, 2016 8:51:03 AM >> >> > > >> > > Subject: Re: [Devtools] Development Suite installation >> >> > > >> > > question - C/O >> >> > > >> > SME with knowledge of installer edits >> >> > > >> > > >> >> > > >> > > On 6.?7.?2016 10:08:09, Rick Wagner wrote: >> >> > > >> > > >> >> > > >> > > > Hello DevTools, >> >> > > >> > > > >> >> > > >> > > > We have a customer case that deals with the error message >> >> > > >> > > > "Terms and >> >> > > >> > > > Conditions for the CDK have not been signed". (Actually, >> >> > > >> > > > this is the >> >> > > >> > > > second case in 2 days for this problem.) >> >> > > >> > > > >> >> > > >> > > > The customer has tried the suggested workaround, without >> >> > > >> > > > satisfactory >> >> > > >> > > > results. ("This error appears on the *Log In* page when >> >> > > >> > > > starting the >> >> > > >> > > > Installer. To fix the problem, start downloading the >> >> > > >> > > > Installer to >> >> > > >> > ensure >> >> > > >> > > > the *Terms and Conditions* are viewed and accepted and >> >> > > >> > > > then cancel the >> >> > > >> > > > binary download." We offer this suggestion in the >> >> > > >> > > > knowledge article at >> >> > > >> > > > [1].) >> >> > > >> > > > >> >> > > >> > > > Can a knowledgeable SME please offer ideas about >> >> > > >> > > > alternative courses of >> >> > > >> > > > action? >> >> > > >> > > >> >> > > >> > > Hi Rick, >> >> > > >> > > >> >> > > >> > > The problem happens quite often, apparently. I asked about >> >> > > >> > > this last >> >> > > >> > Friday >> >> > > >> > > in devtools-program [a] -- on behalf of a user who reported >> >> > > >> > > the problem >> >> > > >> > in a >> >> > > >> > > comment under the old version of the Kbase article [b]. >> >> > > >> > > >> >> > > >> > > Any workaround would be appreciated. >> >> > > >> > > >> >> > > >> > > Thanks. >> >> > > >> > > >> >> > > >> > > Robert >> >> > > >> > > >> >> > > >> > > [a] >> >> > > >> > > >> >> > > >> > >> >> > > >> > http://post-office.corp.redhat.com/archives/devtools-program/2016-July/msg00001.html >> >> > > >> > > [b] >> >> > > >> > > https://access.redhat.com/articles/2255391#comment-1066361 >> >> > > >> > > >> >> > > >> > > > Extra credit: Can you please point me to the source code >> >> > > >> > > > that produces >> >> > > >> > > > this edit error? A little spelunking by the Support team >> >> > > >> > > > sometimes >> >> > > >> > helps >> >> > > >> > > > with related issues. >> >> > > >> > > > >> >> > > >> > > > Thanks! >> >> > > >> > > > >> >> > > >> > > > Rick >> >> > > >> > > > >> >> > > >> > > > [1] https://access.redhat.com/articles/2360571 >> > >> > >> > _______________________________________________ >> > Devtools mailing list >> > Devtools at redhat.com >> > https://www.redhat.com/mailman/listinfo/devtools > > From lmohanty at redhat.com Thu Jul 7 18:35:59 2016 From: lmohanty at redhat.com (Lalatendu Mohanty) Date: Fri, 8 Jul 2016 00:05:59 +0530 Subject: [Devtools] support for OpenShift Container Platform / Origin in minikube? In-Reply-To: References: <34C29FC6-B5F2-439B-95F4-2D42A156E35E@redhat.com> <217D53D0-D256-48E5-8D26-CFD36BF44AC7@redhat.com> <20160706073224.GE96345@nineveh.lan> <9222908504856097678@unknownmsgid> Message-ID: <7fa7422b-38a0-3204-1310-fa7d062fbeb4@redhat.com> On 07/07/2016 10:37 PM, Pete Muir wrote: > On 7 July 2016 at 17:55, Clayton Coleman wrote: >> >> On Thu, Jul 7, 2016 at 12:48 PM, Jimmi Dyson wrote: >>> On 7 July 2016 at 17:36, Pete Muir wrote: >>>> Hardy, Lala and the rest of the ADB team are going to investigate this >>>> over the next few weeks (whether we can replace the ADB infra with >>>> minishift). >>>> >>>> For the product version it must be based on something that we >>>> productise (which currently is RHEL or Atomic AFAIK) - doing it on top >>>> of something like Alpine is not an option. >>> You can see what it's built from at >>> https://hub.docker.com/r/boot2docker/boot2docker/~/dockerfile/ . Don't >>> worry about the FROM debian:jessie - that's just to create the builder >>> image. You can see the minimal stuff it's actually installing in the >>> final ISO. >>> >>>> I would also worry about having a radically different upstream from >>>> the product version, as I think this can cause bugs, but I'll leave >>>> this one to the team to figure out :-) >>>> >>>> I've also asked Ian a few times if we can try to build smaller images >>>> - something to keep trying for ;-) >>> I don't see why we couldn't have the equivalent of boot2docker.iso >>> image that minikube uses: basically a kernel & docker.... that's it. >>> Sure we can use a RHEL/CentOS kernel, right? Just please not the whole >>> RHEL install ;) >> >> Agreed. I think Pete and I are just saying that we need to make an effort >> to fix the actual problem (we don't have a small ISO for RHEL/CentOS that >> represents our strengths in containers), and that we should also be taking >> those steps in parallel. > Exactly. I also still don't understand why we don't ship Atomic Host > as the default OS in the container runtime portion of the CDK - this > seems like an obvious thing to do . I think we should incorporate container runtime portion of Atomic host in CDK. It makes more sense in current context as we are running OpenShift and Kubernetes as containers. Just to add bit of history , when we started CDK 2.0 we were not sure if using Atomic host is a good idea as the file system of Atomic host is read-only except /etc and /var. Also we need to take decision around if we want to keep the Kubernetes single node setup relevant in CDK context as my recent understanding is that we are encouraging users to use OpenShift for Kubernetes specific usage. Thanks, Lala > _______________________________________________ > Devtools mailing list > Devtools at redhat.com > https://www.redhat.com/mailman/listinfo/devtools From lmohanty at redhat.com Thu Jul 7 18:39:54 2016 From: lmohanty at redhat.com (Lalatendu Mohanty) Date: Fri, 8 Jul 2016 00:09:54 +0530 Subject: [Devtools] support for OpenShift Container Platform / Origin in minikube? In-Reply-To: References: <34C29FC6-B5F2-439B-95F4-2D42A156E35E@redhat.com> <217D53D0-D256-48E5-8D26-CFD36BF44AC7@redhat.com> <20160706073224.GE96345@nineveh.lan> <9222908504856097678@unknownmsgid> Message-ID: <75cdd3fe-e618-0a37-2a6a-b49db75729f8@redhat.com> On 07/07/2016 10:25 PM, Clayton Coleman wrote: > > > On Thu, Jul 7, 2016 at 12:48 PM, Jimmi Dyson > wrote: > > On 7 July 2016 at 17:36, Pete Muir > wrote: > > Hardy, Lala and the rest of the ADB team are going to > investigate this > > over the next few weeks (whether we can replace the ADB infra with > > minishift). > > > > For the product version it must be based on something that we > > productise (which currently is RHEL or Atomic AFAIK) - doing it > on top > > of something like Alpine is not an option. > > You can see what it's built from at > https://hub.docker.com/r/boot2docker/boot2docker/~/dockerfile/ > > . Don't > worry about the FROM debian:jessie - that's just to create the builder > image. You can see the minimal stuff it's actually installing in the > final ISO. > > > > > I would also worry about having a radically different upstream from > > the product version, as I think this can cause bugs, but I'll leave > > this one to the team to figure out :-) > > > > I've also asked Ian a few times if we can try to build smaller > images > > - something to keep trying for ;-) > > I don't see why we couldn't have the equivalent of boot2docker.iso > image that minikube uses: basically a kernel & docker.... that's it. > Sure we can use a RHEL/CentOS kernel, right? Just please not the whole > RHEL install ;) > > > Agreed. I think Pete and I are just saying that we need to make an > effort to fix the actual problem (we don't have a small ISO for > RHEL/CentOS that represents our strengths in containers), and that we > should also be taking those steps in parallel. Hi Clayton, I have not tried minishift or "oc cluster up" yet . So I am little confused at this point. Not sure if these two methods competes with each other or not. What is your opinion on this? Thanks, Lala -------------- next part -------------- An HTML attachment was scrubbed... URL: From dusty at dustymabe.com Thu Jul 7 21:12:24 2016 From: dusty at dustymabe.com (Dusty Mabe) Date: Thu, 7 Jul 2016 17:12:24 -0400 Subject: [Devtools] Creation of projectatomic/nulecule-library Docker Hub file In-Reply-To: <20160704182039.GA1@7177a189328f> References: <20160704182039.GA1@7177a189328f> Message-ID: <73e96295-5605-1816-48b3-4ac7b945afad@dustymabe.com> On 07/04/2016 02:20 PM, Charlie Drage wrote: > Hey all, > > With the work I've been doing on the `atomicapp index` PR (well, > picking up on the work that vpavlin did), I require the creation of a > new Docker image that will contain the `index.yaml` file on > hub.docker.com/projectatomic Might be good to have it be more specific than `index.yaml`. Maybe nulecule-library-index.yaml > > I have permission for the files, however, I want people's input before > I add it. > > Should the name be `projectatomic/index` or > `projectatomic/nulecule-library-index` or something of the rather? > > PR source: https://github.com/projectatomic/atomicapp/pull/750 > I would prefer: `projectatomic/nulecule-library-index` or just `projecatomic/nulecule-index` or `projectatomic/nulecule-library`. Let's make it happen. From dusty at dustymabe.com Thu Jul 7 21:13:43 2016 From: dusty at dustymabe.com (Dusty Mabe) Date: Thu, 7 Jul 2016 17:13:43 -0400 Subject: [Devtools] Creation of projectatomic/nulecule-library Docker Hub file In-Reply-To: <20160706190246.GB1@1f9b86abf2d2> References: <20160704182039.GA1@7177a189328f> <577D5467.6030306@dustymabe.com> <20160706190246.GB1@1f9b86abf2d2> Message-ID: <9ce6a60a-87f0-b922-e8a7-ccdb5f53ded2@dustymabe.com> On 07/06/2016 03:02 PM, Charlie Drage wrote: > Yeah, I'm only doing it via container since instead of relying of us > hosting the yaml file, we can rely on the docker hub instead. Gives us > easy access to update it, etc. > > Just going by how vpavlin implemented it too :) > Would be nice to let the user override the index from the command line, either by providing a path to a file, an http location or the name of an alternate dockerfile. Dusty From degolovi at redhat.com Thu Jul 7 23:25:36 2016 From: degolovi at redhat.com (Denis Golovin) Date: Thu, 7 Jul 2016 19:25:36 -0400 (EDT) Subject: [Devtools] Fix an installer problem with a server-side change? In-Reply-To: References: <93417907.3928289.1467844622630.JavaMail.zimbra@redhat.com> <1582948441.3940414.1467850719230.JavaMail.zimbra@redhat.com> Message-ID: <1206314396.4301151.1467933936744.JavaMail.zimbra@redhat.com> Pete, I am sure about social account doesn't work (tried it for google account), it might generated rhd user behind the scene but what username/password is used? gmail email and password doesn't work after registration in my test. Installer uses basic auth only and that requires Red Hat username/password. Denis ----- Original Message ----- > From: "Pete Muir" > To: "Denis Golovin" > Cc: "Rick Wagner" , devtools at redhat.com > Sent: Thursday, July 7, 2016 4:40:03 AM > Subject: Re: [Devtools] Fix an installer problem with a server-side change? > > Denis, are you sure about this? The social account login should > generate a full user, if you do proceed to initiate a download of the > installer. > > On 7 July 2016 at 01:18, Denis Golovin wrote: > > Rick > > > > devsuite installer supports only users with Red Hat Developer Account. > > it means registration with social account doesn't work. > > > > Workaround would be: > > 1. Visit registration here > > https://developers.redhat.com/auth/realms/rhd/login-actions/registration?code=rAAJsUjKrvSMRBFSY5mpfvp87g9LS8Xub8_bjkj7lvI.68060bb4-4525-4f5f-98aa-98651b2fab74 > > 2. then use e-mail/password in devsuite installer > > > > Denis > > > > ----- Original Message ----- > >> From: "Denis Golovin" > >> To: "Rick Wagner" > >> Cc: devtools at redhat.com > >> Sent: Wednesday, July 6, 2016 3:37:02 PM > >> Subject: Re: [Devtools] Fix an installer problem with a server-side > >> change? > >> > >> Rick, > >> > >> minor correction for curl command. It should be issued with -s option to > >> suppress progress bar. > >> The output would be true/false/Invalid user credentials for user > >> username at mailserver.com. > >> > >> Denis > >> > >> > >> ----- Original Message ----- > >> > From: "Rick Wagner" > >> > To: devtools at redhat.com, "Denis Golovin" > >> > Sent: Wednesday, July 6, 2016 2:03:49 PM > >> > Subject: Re: [Devtools] Fix an installer problem with a server-side > >> > change? > >> > > >> > Hi Denis, > >> > > >> > Thanks much for that idea. > >> > > >> > I've written our customers, let's see if they can coax a 'true' out of > >> > curl. That may help us get to the bottom of the problem, let's see. > >> > > >> > Rick > >> > > >> > ------------------------------ > >> > > >> > Message: 6 > >> > Date: Wed, 6 Jul 2016 16:11:23 -0400 (EDT) > >> > From: Denis Golovin > >> > To: Rick Wagner > >> > Cc: devtools at redhat.com > >> > Subject: Re: [Devtools] Fix an installer problem with a server-side > >> > change? > >> > Message-ID: > >> > <2069914337.3902671.1467835883831.JavaMail.zimbra at redhat.com> > >> > Content-Type: text/plain; charset=utf-8 > >> > > >> > Rick, > >> > > >> > This should be the case for those who hasn't downloaded devsuite > >> > directly > >> > from > >> > developer.redhat.com. Workaround mentioned in documentation should work > >> > and > >> > I walking > >> > throw this workflow from scratch to verify nothing is changed since I > >> > did > >> > it last time > >> > right before summit. > >> > > >> > Simple test is > >> > > >> > curl https://username%40mailserver.com:p > >> > assword at developers.redhat.com/download-manager/rest/tc-accepted?downloadURL=/file/cdk-2.0.0-beta3.zip > >> > > >> > works for users previously signed T&C's before download from > >> > develoers.redhat.com. > >> > > >> > > >> > Just changing rest would not work as I understand, because additional > >> > information in > >> > profile is required before developer with developer.redhat.com account > >> > can > >> > proceed with > >> > T&C's signing. > >> > > >> > > >> > Denis > >> > > >> > >> _______________________________________________ > >> 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 > From degolovi at redhat.com Thu Jul 7 23:27:20 2016 From: degolovi at redhat.com (Denis Golovin) Date: Thu, 7 Jul 2016 19:27:20 -0400 (EDT) Subject: [Devtools] Fix an installer problem with a server-side change? In-Reply-To: References: Message-ID: <286619954.4301173.1467934040488.JavaMail.zimbra@redhat.com> That is correct answer. This url is only to verify T&C's are signed. ----- Original Message ----- > From: "Pavol Pitonak" > To: "Pete Muir" > Cc: devtools at redhat.com, "Rick Wagner" > Sent: Thursday, July 7, 2016 4:50:19 AM > Subject: Re: [Devtools] Fix an installer problem with a server-side change? > > It's not installing CDK 2.0.0-beta3 but the one specified in [1]. The > mentioned URL is only used for finding out whether the user provided correct > username/password and whether he had agreed with T&C. > > [1] > https://github.com/redhat-developer-tooling/developer-platform-install/blob/master/requirements.json#L7 > > On Thu, Jul 7, 2016 at 1:40 PM, Pete Muir < pmuir at redhat.com > wrote: > > > On 6 July 2016 at 20:02, Rick Wagner < rwagner at redhat.com > wrote: > > Hello DevTools, > > > > It seems we have a problem with the current version of the Development > > Suite > > installer. We have at least 2 new customer cases reporting inability to > > install due to the message dialogue "Terms and Conditions for the CDK have > > not been signed". > > > > This is concerning because we're also seeing similar activity on > > non-support > > channels. It's also worth noting that not every user that has a problem > > reports it-- some just give up and move on. There is enough volume here > > that we probably should treat this with some urgency. > > > > It seems likely the relevant code (thanks for highlighting this, Alexey) is > > below: > > > > ------------------------------------------------- > > > > login() { > > this.authFailed = false; > > this.tandcNotSigned = false; > > > > let req = { > > method: 'GET', > > url: > > ' > > https://developers.redhat.com/download-manager/rest/tc-accepted?downloadURL=/file/cdk-2.0.0-beta3.zip > > ', > > <<<<<<<<<---- returns 'false' when not approved > > I noticed when reading this that this code appears to be downloading > CDK 2.0.0-beta3 which implies that either this is an old version of > the installer, or the installer is installing a very old CDK... > > > headers: { > > 'Authorization': 'Basic ' + this.base64.encode(this.username + ':' + > > this.password) > > } > > }; > > > > this.http(req) > > .then(this.handleHttpSuccess.bind(this)) > > .catch(this.handleHttpFailure.bind(this)); > > } > > > > --------------------------------- > > > > > > So we have users getting denied use of our product. Do we require a rebuild > > immediately? Maybe. > > > > How about if we changed the rest service > > ( https://developers.redhat.com/download-manager/rest/tc-accepted ) so it > > includes a peak at an override database as well as whatever it's currently > > doing now? > > > > In that way, we could have the users pop over to a 'yes, I agree to the > > terms' page to insert an entry into the database. The rest service could > > use something like the provided username as a key to ensure a 'true' is > > returned. > > > > > > Or not. Is there a better way to fix this? > > > > Please consider, we need to fix this sooner rather than later.... > > > > Thanks, > > > > Rick > > > > > > _______________________________________________ > > 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 > From degolovi at redhat.com Thu Jul 7 23:32:41 2016 From: degolovi at redhat.com (Denis Golovin) Date: Thu, 7 Jul 2016 19:32:41 -0400 (EDT) Subject: [Devtools] Fix an installer problem with a server-side change? In-Reply-To: References: <93417907.3928289.1467844622630.JavaMail.zimbra@redhat.com> <1582948441.3940414.1467850719230.JavaMail.zimbra@redhat.com> Message-ID: <1056427860.4302235.1467934361546.JavaMail.zimbra@redhat.com> Rick, I've never seen that one. Installer interpretation would be 'T&C's are not signed', which is probably not right and should be something 'Cannot verify T&C's please login again'. Denis ----- Original Message ----- > From: "Rick Wagner" > To: "Denis Golovin" > Cc: devtools at redhat.com > Sent: Thursday, July 7, 2016 5:12:55 AM > Subject: Re: [Devtools] Fix an installer problem with a server-side change? > > Hi Denis, > > That link gets me an error page that reads "We're sorry.... An error > occurred, please login again through your application". > > Do we expect the customers with failing installations will have a different > result? > > Thanks, > > Rick > > > > On Wed, Jul 6, 2016 at 7:18 PM, Denis Golovin wrote: > > > Rick > > > > devsuite installer supports only users with Red Hat Developer Account. > > it means registration with social account doesn't work. > > > > Workaround would be: > > 1. Visit registration here > > > > https://developers.redhat.com/auth/realms/rhd/login-actions/registration?code=rAAJsUjKrvSMRBFSY5mpfvp87g9LS8Xub8_bjkj7lvI.68060bb4-4525-4f5f-98aa-98651b2fab74 > > 2. then use e-mail/password in devsuite installer > > > > Denis > > > > ----- Original Message ----- > > > From: "Denis Golovin" > > > To: "Rick Wagner" > > > Cc: devtools at redhat.com > > > Sent: Wednesday, July 6, 2016 3:37:02 PM > > > Subject: Re: [Devtools] Fix an installer problem with a server-side > > change? > > > > > > Rick, > > > > > > minor correction for curl command. It should be issued with -s option to > > > suppress progress bar. > > > The output would be true/false/Invalid user credentials for user > > > username at mailserver.com. > > > > > > Denis > > > > > > > > > ----- Original Message ----- > > > > From: "Rick Wagner" > > > > To: devtools at redhat.com, "Denis Golovin" > > > > Sent: Wednesday, July 6, 2016 2:03:49 PM > > > > Subject: Re: [Devtools] Fix an installer problem with a server-side > > change? > > > > > > > > Hi Denis, > > > > > > > > Thanks much for that idea. > > > > > > > > I've written our customers, let's see if they can coax a 'true' out of > > > > curl. That may help us get to the bottom of the problem, let's see. > > > > > > > > Rick > > > > > > > > ------------------------------ > > > > > > > > Message: 6 > > > > Date: Wed, 6 Jul 2016 16:11:23 -0400 (EDT) > > > > From: Denis Golovin > > > > To: Rick Wagner > > > > Cc: devtools at redhat.com > > > > Subject: Re: [Devtools] Fix an installer problem with a server-side > > > > change? > > > > Message-ID: > > > > <2069914337.3902671.1467835883831.JavaMail.zimbra at redhat.com> > > > > Content-Type: text/plain; charset=utf-8 > > > > > > > > Rick, > > > > > > > > This should be the case for those who hasn't downloaded devsuite > > directly > > > > from > > > > developer.redhat.com. Workaround mentioned in documentation should > > work and > > > > I walking > > > > throw this workflow from scratch to verify nothing is changed since I > > did > > > > it last time > > > > right before summit. > > > > > > > > Simple test is > > > > > > > > curl https://username%40mailserver.com:p > > > > > > assword at developers.redhat.com/download-manager/rest/tc-accepted?downloadURL=/file/cdk-2.0.0-beta3.zip > > > > > > > > works for users previously signed T&C's before download from > > > > develoers.redhat.com. > > > > > > > > > > > > Just changing rest would not work as I understand, because additional > > > > information in > > > > profile is required before developer with developer.redhat.com > > account can > > > > proceed with > > > > T&C's signing. > > > > > > > > > > > > Denis > > > > > > > > > > _______________________________________________ > > > Devtools mailing list > > > Devtools at redhat.com > > > https://www.redhat.com/mailman/listinfo/devtools > > > > > > From prkumar at redhat.com Fri Jul 8 06:48:52 2016 From: prkumar at redhat.com (Praveen Kumar) Date: Fri, 8 Jul 2016 12:18:52 +0530 Subject: [Devtools] support for OpenShift Container Platform / Origin in minikube? In-Reply-To: <75cdd3fe-e618-0a37-2a6a-b49db75729f8@redhat.com> References: <34C29FC6-B5F2-439B-95F4-2D42A156E35E@redhat.com> <217D53D0-D256-48E5-8D26-CFD36BF44AC7@redhat.com> <20160706073224.GE96345@nineveh.lan> <9222908504856097678@unknownmsgid> <75cdd3fe-e618-0a37-2a6a-b49db75729f8@redhat.com> Message-ID: On Fri, Jul 8, 2016 at 12:09 AM, Lalatendu Mohanty wrote: > > Hi Clayton, > > I have not tried minishift or "oc cluster up" yet . So I am little confused > at this point. Not sure if these two methods competes with each other or > not. What is your opinion on this? I did try both, minishift is for creating the environment (on different platform) then running openshift binary (as of now). Now we can use 'oc cluster up' once we have have endpoints of deployed openshift server using minishift which currently is not working[0] but I think this is the idea. [0] https://github.com/jimmidyson/minishift/issues/2 -- Praveen Kumar https://fedoraproject.org/wiki/User:Kumarpraveen From jdyson at redhat.com Fri Jul 8 11:17:10 2016 From: jdyson at redhat.com (Jimmi Dyson) Date: Fri, 8 Jul 2016 12:17:10 +0100 Subject: [Devtools] support for OpenShift Container Platform / Origin in minikube? In-Reply-To: References: <34C29FC6-B5F2-439B-95F4-2D42A156E35E@redhat.com> <217D53D0-D256-48E5-8D26-CFD36BF44AC7@redhat.com> <20160706073224.GE96345@nineveh.lan> <9222908504856097678@unknownmsgid> <75cdd3fe-e618-0a37-2a6a-b49db75729f8@redhat.com> Message-ID: On 8 July 2016 at 07:48, Praveen Kumar wrote: > On Fri, Jul 8, 2016 at 12:09 AM, Lalatendu Mohanty wrote: >> >> Hi Clayton, >> >> I have not tried minishift or "oc cluster up" yet . So I am little confused >> at this point. Not sure if these two methods competes with each other or >> not. What is your opinion on this? > > > I did try both, minishift is for creating the environment (on > different platform) then running openshift binary (as of now). Now we > can use 'oc cluster up' once we have have endpoints of deployed > openshift server using minishift which currently is not working[0] but > I think this is the idea. The idea is that you shouldn't need to run `oc cluster up` as `minishift start` is the equivalent command. Right now it does a bit less than `oc cluster up`, not installing registry/router which may see like overkill for most dev tasks where you can simply use the VM's Docker daemon for image builds, etc & perhaps relying on NodePort services for connecting in to your service from the host. This keeps footprint as small as possible (running a registry & router obviously requires resources) while allowing most dev tasks, at the expense of the full production style deployment. I feel that's a reasonable trade off for a local dev kit. > > [0] https://github.com/jimmidyson/minishift/issues/2 This is now fixed btw - try out v0.1.1 (https://github.com/jimmidyson/minishift/releases/tag/v0.1.1). > > -- > Praveen Kumar > https://fedoraproject.org/wiki/User:Kumarpraveen From hferents at redhat.com Fri Jul 8 12:17:14 2016 From: hferents at redhat.com (Hardy Ferentschik) Date: Fri, 8 Jul 2016 14:17:14 +0200 Subject: [Devtools] support for OpenShift Container Platform / Origin in minikube? In-Reply-To: <9222908504856097678@unknownmsgid> References: <34C29FC6-B5F2-439B-95F4-2D42A156E35E@redhat.com> <217D53D0-D256-48E5-8D26-CFD36BF44AC7@redhat.com> <20160706073224.GE96345@nineveh.lan> <9222908504856097678@unknownmsgid> Message-ID: <20160708121714.GD19484@nineveh.lan> Hi, > Not running the Red Hat Docker is a serious problem for OpenShift / > Kube, simply given the instability and gaps in upstream Docker. While > we're not running production workloads, it's really difficult to > certify and fix issues. Here is a bit I don't understand. We keep saying we should run the Red Hat Docker and somehow this seems to imply that you also need the CentOS/RHEL base image. Can one not replace the default Docker binary of any distribution with the Red Hat version? Or does the Red Hat version depend on things which are only available on RHEL. My understanding was that Red Hat even offered a patch for Docker, but they are just not willing to accept this. So there should be not extras required, right? --Hardy -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 496 bytes Desc: not available URL: From hferents at redhat.com Fri Jul 8 12:21:06 2016 From: hferents at redhat.com (Hardy Ferentschik) Date: Fri, 8 Jul 2016 14:21:06 +0200 Subject: [Devtools] support for OpenShift Container Platform / Origin in minikube? In-Reply-To: References: <217D53D0-D256-48E5-8D26-CFD36BF44AC7@redhat.com> <20160706073224.GE96345@nineveh.lan> <9222908504856097678@unknownmsgid> Message-ID: <20160708122106.GE19484@nineveh.lan> Hi, > Agreed. I think Pete and I are just saying that we need to make an effort > to fix the actual problem (we don't have a small ISO for RHEL/CentOS that > represents our strengths in containers), and that we should also be taking > those steps in parallel. +1 Being able to build a minimal RHEL/CentOS would be a big step forward. Not only in the context of minishift, but also for ADB/CDK. The big image size makes downloads big and creates long waiting and startup times. And of course increases the overall memory footprint. --Hardy -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 496 bytes Desc: not available URL: From pmuir at redhat.com Fri Jul 8 14:51:37 2016 From: pmuir at redhat.com (Pete Muir) Date: Fri, 8 Jul 2016 15:51:37 +0100 Subject: [Devtools] Fix an installer problem with a server-side change? In-Reply-To: <1206314396.4301151.1467933936744.JavaMail.zimbra@redhat.com> References: <93417907.3928289.1467844622630.JavaMail.zimbra@redhat.com> <1582948441.3940414.1467850719230.JavaMail.zimbra@redhat.com> <1206314396.4301151.1467933936744.JavaMail.zimbra@redhat.com> Message-ID: Hi Denis, It definitely works with the current account creation process. The account creation requests a username (email) and password when you create a new account with a google social login. http://www.screencast.com/t/rFlNXqz1GbXw Pete On 8 July 2016 at 00:25, Denis Golovin wrote: > Pete, > > I am sure about social account doesn't work (tried it for google account), it might generated rhd user behind the scene but what username/password is used? > gmail email and password doesn't work after registration in my test. > > Installer uses basic auth only and that requires Red Hat username/password. > > Denis > ----- Original Message ----- >> From: "Pete Muir" >> To: "Denis Golovin" >> Cc: "Rick Wagner" , devtools at redhat.com >> Sent: Thursday, July 7, 2016 4:40:03 AM >> Subject: Re: [Devtools] Fix an installer problem with a server-side change? >> >> Denis, are you sure about this? The social account login should >> generate a full user, if you do proceed to initiate a download of the >> installer. >> >> On 7 July 2016 at 01:18, Denis Golovin wrote: >> > Rick >> > >> > devsuite installer supports only users with Red Hat Developer Account. >> > it means registration with social account doesn't work. >> > >> > Workaround would be: >> > 1. Visit registration here >> > https://developers.redhat.com/auth/realms/rhd/login-actions/registration?code=rAAJsUjKrvSMRBFSY5mpfvp87g9LS8Xub8_bjkj7lvI.68060bb4-4525-4f5f-98aa-98651b2fab74 >> > 2. then use e-mail/password in devsuite installer >> > >> > Denis >> > >> > ----- Original Message ----- >> >> From: "Denis Golovin" >> >> To: "Rick Wagner" >> >> Cc: devtools at redhat.com >> >> Sent: Wednesday, July 6, 2016 3:37:02 PM >> >> Subject: Re: [Devtools] Fix an installer problem with a server-side >> >> change? >> >> >> >> Rick, >> >> >> >> minor correction for curl command. It should be issued with -s option to >> >> suppress progress bar. >> >> The output would be true/false/Invalid user credentials for user >> >> username at mailserver.com. >> >> >> >> Denis >> >> >> >> >> >> ----- Original Message ----- >> >> > From: "Rick Wagner" >> >> > To: devtools at redhat.com, "Denis Golovin" >> >> > Sent: Wednesday, July 6, 2016 2:03:49 PM >> >> > Subject: Re: [Devtools] Fix an installer problem with a server-side >> >> > change? >> >> > >> >> > Hi Denis, >> >> > >> >> > Thanks much for that idea. >> >> > >> >> > I've written our customers, let's see if they can coax a 'true' out of >> >> > curl. That may help us get to the bottom of the problem, let's see. >> >> > >> >> > Rick >> >> > >> >> > ------------------------------ >> >> > >> >> > Message: 6 >> >> > Date: Wed, 6 Jul 2016 16:11:23 -0400 (EDT) >> >> > From: Denis Golovin >> >> > To: Rick Wagner >> >> > Cc: devtools at redhat.com >> >> > Subject: Re: [Devtools] Fix an installer problem with a server-side >> >> > change? >> >> > Message-ID: >> >> > <2069914337.3902671.1467835883831.JavaMail.zimbra at redhat.com> >> >> > Content-Type: text/plain; charset=utf-8 >> >> > >> >> > Rick, >> >> > >> >> > This should be the case for those who hasn't downloaded devsuite >> >> > directly >> >> > from >> >> > developer.redhat.com. Workaround mentioned in documentation should work >> >> > and >> >> > I walking >> >> > throw this workflow from scratch to verify nothing is changed since I >> >> > did >> >> > it last time >> >> > right before summit. >> >> > >> >> > Simple test is >> >> > >> >> > curl https://username%40mailserver.com:p >> >> > assword at developers.redhat.com/download-manager/rest/tc-accepted?downloadURL=/file/cdk-2.0.0-beta3.zip >> >> > >> >> > works for users previously signed T&C's before download from >> >> > develoers.redhat.com. >> >> > >> >> > >> >> > Just changing rest would not work as I understand, because additional >> >> > information in >> >> > profile is required before developer with developer.redhat.com account >> >> > can >> >> > proceed with >> >> > T&C's signing. >> >> > >> >> > >> >> > Denis >> >> > >> >> >> >> _______________________________________________ >> >> 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 >> From pmuir at redhat.com Fri Jul 8 14:52:30 2016 From: pmuir at redhat.com (Pete Muir) Date: Fri, 8 Jul 2016 15:52:30 +0100 Subject: [Devtools] Fix an installer problem with a server-side change? In-Reply-To: <286619954.4301173.1467934040488.JavaMail.zimbra@redhat.com> References: <286619954.4301173.1467934040488.JavaMail.zimbra@redhat.com> Message-ID: Do we have an issue to replace this with a proper T&C check that doesn't involve the name of a file that might get changed without someone understanding the installer depends on it? On 8 July 2016 at 00:27, Denis Golovin wrote: > That is correct answer. This url is only to verify T&C's are signed. > > ----- Original Message ----- >> From: "Pavol Pitonak" >> To: "Pete Muir" >> Cc: devtools at redhat.com, "Rick Wagner" >> Sent: Thursday, July 7, 2016 4:50:19 AM >> Subject: Re: [Devtools] Fix an installer problem with a server-side change? >> >> It's not installing CDK 2.0.0-beta3 but the one specified in [1]. The >> mentioned URL is only used for finding out whether the user provided correct >> username/password and whether he had agreed with T&C. >> >> [1] >> https://github.com/redhat-developer-tooling/developer-platform-install/blob/master/requirements.json#L7 >> >> On Thu, Jul 7, 2016 at 1:40 PM, Pete Muir < pmuir at redhat.com > wrote: >> >> >> On 6 July 2016 at 20:02, Rick Wagner < rwagner at redhat.com > wrote: >> > Hello DevTools, >> > >> > It seems we have a problem with the current version of the Development >> > Suite >> > installer. We have at least 2 new customer cases reporting inability to >> > install due to the message dialogue "Terms and Conditions for the CDK have >> > not been signed". >> > >> > This is concerning because we're also seeing similar activity on >> > non-support >> > channels. It's also worth noting that not every user that has a problem >> > reports it-- some just give up and move on. There is enough volume here >> > that we probably should treat this with some urgency. >> > >> > It seems likely the relevant code (thanks for highlighting this, Alexey) is >> > below: >> > >> > ------------------------------------------------- >> > >> > login() { >> > this.authFailed = false; >> > this.tandcNotSigned = false; >> > >> > let req = { >> > method: 'GET', >> > url: >> > ' >> > https://developers.redhat.com/download-manager/rest/tc-accepted?downloadURL=/file/cdk-2.0.0-beta3.zip >> > ', >> > <<<<<<<<<---- returns 'false' when not approved >> >> I noticed when reading this that this code appears to be downloading >> CDK 2.0.0-beta3 which implies that either this is an old version of >> the installer, or the installer is installing a very old CDK... >> >> > headers: { >> > 'Authorization': 'Basic ' + this.base64.encode(this.username + ':' + >> > this.password) >> > } >> > }; >> > >> > this.http(req) >> > .then(this.handleHttpSuccess.bind(this)) >> > .catch(this.handleHttpFailure.bind(this)); >> > } >> > >> > --------------------------------- >> > >> > >> > So we have users getting denied use of our product. Do we require a rebuild >> > immediately? Maybe. >> > >> > How about if we changed the rest service >> > ( https://developers.redhat.com/download-manager/rest/tc-accepted ) so it >> > includes a peak at an override database as well as whatever it's currently >> > doing now? >> > >> > In that way, we could have the users pop over to a 'yes, I agree to the >> > terms' page to insert an entry into the database. The rest service could >> > use something like the provided username as a key to ensure a 'true' is >> > returned. >> > >> > >> > Or not. Is there a better way to fix this? >> > >> > Please consider, we need to fix this sooner rather than later.... >> > >> > Thanks, >> > >> > Rick >> > >> > >> > _______________________________________________ >> > 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 >> From pmuir at redhat.com Fri Jul 8 15:03:15 2016 From: pmuir at redhat.com (Pete Muir) Date: Fri, 8 Jul 2016 16:03:15 +0100 Subject: [Devtools] support for OpenShift Container Platform / Origin in minikube? In-Reply-To: <7fa7422b-38a0-3204-1310-fa7d062fbeb4@redhat.com> References: <34C29FC6-B5F2-439B-95F4-2D42A156E35E@redhat.com> <217D53D0-D256-48E5-8D26-CFD36BF44AC7@redhat.com> <20160706073224.GE96345@nineveh.lan> <9222908504856097678@unknownmsgid> <7fa7422b-38a0-3204-1310-fa7d062fbeb4@redhat.com> Message-ID: On 7 July 2016 at 19:35, Lalatendu Mohanty wrote: > On 07/07/2016 10:37 PM, Pete Muir wrote: >> >> On 7 July 2016 at 17:55, Clayton Coleman wrote: >>> >>> >>> On Thu, Jul 7, 2016 at 12:48 PM, Jimmi Dyson wrote: >>>> >>>> On 7 July 2016 at 17:36, Pete Muir wrote: >>>>> >>>>> Hardy, Lala and the rest of the ADB team are going to investigate this >>>>> over the next few weeks (whether we can replace the ADB infra with >>>>> minishift). >>>>> >>>>> For the product version it must be based on something that we >>>>> productise (which currently is RHEL or Atomic AFAIK) - doing it on top >>>>> of something like Alpine is not an option. >>>> >>>> You can see what it's built from at >>>> https://hub.docker.com/r/boot2docker/boot2docker/~/dockerfile/ . Don't >>>> worry about the FROM debian:jessie - that's just to create the builder >>>> image. You can see the minimal stuff it's actually installing in the >>>> final ISO. >>>> >>>>> I would also worry about having a radically different upstream from >>>>> the product version, as I think this can cause bugs, but I'll leave >>>>> this one to the team to figure out :-) >>>>> >>>>> I've also asked Ian a few times if we can try to build smaller images >>>>> - something to keep trying for ;-) >>>> >>>> I don't see why we couldn't have the equivalent of boot2docker.iso >>>> image that minikube uses: basically a kernel & docker.... that's it. >>>> Sure we can use a RHEL/CentOS kernel, right? Just please not the whole >>>> RHEL install ;) >>> >>> >>> Agreed. I think Pete and I are just saying that we need to make an >>> effort >>> to fix the actual problem (we don't have a small ISO for RHEL/CentOS that >>> represents our strengths in containers), and that we should also be >>> taking >>> those steps in parallel. >> >> Exactly. I also still don't understand why we don't ship Atomic Host >> as the default OS in the container runtime portion of the CDK - this >> seems like an obvious thing to do . > > > I think we should incorporate container runtime portion of Atomic host in > CDK. It makes more sense in current context as we are running OpenShift and > Kubernetes as containers. Just to add bit of history , when we started CDK > 2.0 we were not sure if using Atomic host is a good idea as the file system > of Atomic host is read-only except /etc and /var. > > Also we need to take decision around if we want to keep the Kubernetes > single node setup relevant in CDK context as my recent understanding is that > we are encouraging users to use OpenShift for Kubernetes specific usage. I would suggest raising this again in about 4 weeks if you haven't got a decision - we aren't quite there yet. > > Thanks, > Lala > >> _______________________________________________ >> 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 From degolovi at redhat.com Sat Jul 9 07:20:04 2016 From: degolovi at redhat.com (Denis Golovin) Date: Sat, 9 Jul 2016 03:20:04 -0400 (EDT) Subject: [Devtools] Fix an installer problem with a server-side change? In-Reply-To: References: <93417907.3928289.1467844622630.JavaMail.zimbra@redhat.com> <1582948441.3940414.1467850719230.JavaMail.zimbra@redhat.com> <1206314396.4301151.1467933936744.JavaMail.zimbra@redhat.com> Message-ID: <1306655417.4729811.1468048804436.JavaMail.zimbra@redhat.com> I distinctly remember there were two fields 'User name' and 'Email', now it works for me the same way as on your screencast and nou username field. Denis ----- Original Message ----- > From: "Pete Muir" > To: "Denis Golovin" > Cc: "Rick Wagner" , devtools at redhat.com > Sent: Friday, July 8, 2016 7:51:37 AM > Subject: Re: [Devtools] Fix an installer problem with a server-side change? > > Hi Denis, > > It definitely works with the current account creation process. The > account creation requests a username (email) and password when you > create a new account with a google social login. > > http://www.screencast.com/t/rFlNXqz1GbXw > > Pete > > On 8 July 2016 at 00:25, Denis Golovin wrote: > > Pete, > > > > I am sure about social account doesn't work (tried it for google account), > > it might generated rhd user behind the scene but what username/password is > > used? > > gmail email and password doesn't work after registration in my test. > > > > Installer uses basic auth only and that requires Red Hat username/password. > > > > Denis > > ----- Original Message ----- > >> From: "Pete Muir" > >> To: "Denis Golovin" > >> Cc: "Rick Wagner" , devtools at redhat.com > >> Sent: Thursday, July 7, 2016 4:40:03 AM > >> Subject: Re: [Devtools] Fix an installer problem with a server-side > >> change? > >> > >> Denis, are you sure about this? The social account login should > >> generate a full user, if you do proceed to initiate a download of the > >> installer. > >> > >> On 7 July 2016 at 01:18, Denis Golovin wrote: > >> > Rick > >> > > >> > devsuite installer supports only users with Red Hat Developer Account. > >> > it means registration with social account doesn't work. > >> > > >> > Workaround would be: > >> > 1. Visit registration here > >> > https://developers.redhat.com/auth/realms/rhd/login-actions/registration?code=rAAJsUjKrvSMRBFSY5mpfvp87g9LS8Xub8_bjkj7lvI.68060bb4-4525-4f5f-98aa-98651b2fab74 > >> > 2. then use e-mail/password in devsuite installer > >> > > >> > Denis > >> > > >> > ----- Original Message ----- > >> >> From: "Denis Golovin" > >> >> To: "Rick Wagner" > >> >> Cc: devtools at redhat.com > >> >> Sent: Wednesday, July 6, 2016 3:37:02 PM > >> >> Subject: Re: [Devtools] Fix an installer problem with a server-side > >> >> change? > >> >> > >> >> Rick, > >> >> > >> >> minor correction for curl command. It should be issued with -s option > >> >> to > >> >> suppress progress bar. > >> >> The output would be true/false/Invalid user credentials for user > >> >> username at mailserver.com. > >> >> > >> >> Denis > >> >> > >> >> > >> >> ----- Original Message ----- > >> >> > From: "Rick Wagner" > >> >> > To: devtools at redhat.com, "Denis Golovin" > >> >> > Sent: Wednesday, July 6, 2016 2:03:49 PM > >> >> > Subject: Re: [Devtools] Fix an installer problem with a server-side > >> >> > change? > >> >> > > >> >> > Hi Denis, > >> >> > > >> >> > Thanks much for that idea. > >> >> > > >> >> > I've written our customers, let's see if they can coax a 'true' out > >> >> > of > >> >> > curl. That may help us get to the bottom of the problem, let's see. > >> >> > > >> >> > Rick > >> >> > > >> >> > ------------------------------ > >> >> > > >> >> > Message: 6 > >> >> > Date: Wed, 6 Jul 2016 16:11:23 -0400 (EDT) > >> >> > From: Denis Golovin > >> >> > To: Rick Wagner > >> >> > Cc: devtools at redhat.com > >> >> > Subject: Re: [Devtools] Fix an installer problem with a server-side > >> >> > change? > >> >> > Message-ID: > >> >> > <2069914337.3902671.1467835883831.JavaMail.zimbra at redhat.com> > >> >> > Content-Type: text/plain; charset=utf-8 > >> >> > > >> >> > Rick, > >> >> > > >> >> > This should be the case for those who hasn't downloaded devsuite > >> >> > directly > >> >> > from > >> >> > developer.redhat.com. Workaround mentioned in documentation should > >> >> > work > >> >> > and > >> >> > I walking > >> >> > throw this workflow from scratch to verify nothing is changed since I > >> >> > did > >> >> > it last time > >> >> > right before summit. > >> >> > > >> >> > Simple test is > >> >> > > >> >> > curl https://username%40mailserver.com:p > >> >> > assword at developers.redhat.com/download-manager/rest/tc-accepted?downloadURL=/file/cdk-2.0.0-beta3.zip > >> >> > > >> >> > works for users previously signed T&C's before download from > >> >> > develoers.redhat.com. > >> >> > > >> >> > > >> >> > Just changing rest would not work as I understand, because additional > >> >> > information in > >> >> > profile is required before developer with developer.redhat.com > >> >> > account > >> >> > can > >> >> > proceed with > >> >> > T&C's signing. > >> >> > > >> >> > > >> >> > Denis > >> >> > > >> >> > >> >> _______________________________________________ > >> >> 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 > >> > From degolovi at redhat.com Sat Jul 9 07:43:21 2016 From: degolovi at redhat.com (Denis Golovin) Date: Sat, 9 Jul 2016 03:43:21 -0400 (EDT) Subject: [Devtools] Fix an installer problem with a server-side change? In-Reply-To: References: <286619954.4301173.1467934040488.JavaMail.zimbra@redhat.com> Message-ID: <1389444465.4733098.1468050201343.JavaMail.zimbra@redhat.com> There is no issue opened for this. Do you mean rest service should support requests to check T&C's using product-id instead of specific file. Something similar to https://developers.redhat.com/download-manager/rest/tc-accepted?productId=cdk ----- Original Message ----- > From: "Pete Muir" > To: "Denis Golovin" > Cc: "Pavol Pitonak" , devtools at redhat.com, "Rick Wagner" > Sent: Friday, July 8, 2016 7:52:30 AM > Subject: Re: [Devtools] Fix an installer problem with a server-side change? > > Do we have an issue to replace this with a proper T&C check that > doesn't involve the name of a file that might get changed without > someone understanding the installer depends on it? > > On 8 July 2016 at 00:27, Denis Golovin wrote: > > That is correct answer. This url is only to verify T&C's are signed. > > > > ----- Original Message ----- > >> From: "Pavol Pitonak" > >> To: "Pete Muir" > >> Cc: devtools at redhat.com, "Rick Wagner" > >> Sent: Thursday, July 7, 2016 4:50:19 AM > >> Subject: Re: [Devtools] Fix an installer problem with a server-side > >> change? > >> > >> It's not installing CDK 2.0.0-beta3 but the one specified in [1]. The > >> mentioned URL is only used for finding out whether the user provided > >> correct > >> username/password and whether he had agreed with T&C. > >> > >> [1] > >> https://github.com/redhat-developer-tooling/developer-platform-install/blob/master/requirements.json#L7 > >> > >> On Thu, Jul 7, 2016 at 1:40 PM, Pete Muir < pmuir at redhat.com > wrote: > >> > >> > >> On 6 July 2016 at 20:02, Rick Wagner < rwagner at redhat.com > wrote: > >> > Hello DevTools, > >> > > >> > It seems we have a problem with the current version of the Development > >> > Suite > >> > installer. We have at least 2 new customer cases reporting inability to > >> > install due to the message dialogue "Terms and Conditions for the CDK > >> > have > >> > not been signed". > >> > > >> > This is concerning because we're also seeing similar activity on > >> > non-support > >> > channels. It's also worth noting that not every user that has a problem > >> > reports it-- some just give up and move on. There is enough volume here > >> > that we probably should treat this with some urgency. > >> > > >> > It seems likely the relevant code (thanks for highlighting this, Alexey) > >> > is > >> > below: > >> > > >> > ------------------------------------------------- > >> > > >> > login() { > >> > this.authFailed = false; > >> > this.tandcNotSigned = false; > >> > > >> > let req = { > >> > method: 'GET', > >> > url: > >> > ' > >> > https://developers.redhat.com/download-manager/rest/tc-accepted?downloadURL=/file/cdk-2.0.0-beta3.zip > >> > ', > >> > <<<<<<<<<---- returns 'false' when not approved > >> > >> I noticed when reading this that this code appears to be downloading > >> CDK 2.0.0-beta3 which implies that either this is an old version of > >> the installer, or the installer is installing a very old CDK... > >> > >> > headers: { > >> > 'Authorization': 'Basic ' + this.base64.encode(this.username + ':' + > >> > this.password) > >> > } > >> > }; > >> > > >> > this.http(req) > >> > .then(this.handleHttpSuccess.bind(this)) > >> > .catch(this.handleHttpFailure.bind(this)); > >> > } > >> > > >> > --------------------------------- > >> > > >> > > >> > So we have users getting denied use of our product. Do we require a > >> > rebuild > >> > immediately? Maybe. > >> > > >> > How about if we changed the rest service > >> > ( https://developers.redhat.com/download-manager/rest/tc-accepted ) so > >> > it > >> > includes a peak at an override database as well as whatever it's > >> > currently > >> > doing now? > >> > > >> > In that way, we could have the users pop over to a 'yes, I agree to the > >> > terms' page to insert an entry into the database. The rest service could > >> > use something like the provided username as a key to ensure a 'true' is > >> > returned. > >> > > >> > > >> > Or not. Is there a better way to fix this? > >> > > >> > Please consider, we need to fix this sooner rather than later.... > >> > > >> > Thanks, > >> > > >> > Rick > >> > > >> > > >> > _______________________________________________ > >> > 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 > >> > From pmuir at redhat.com Mon Jul 11 11:32:56 2016 From: pmuir at redhat.com (Pete Muir) Date: Mon, 11 Jul 2016 12:32:56 +0100 Subject: [Devtools] Fix an installer problem with a server-side change? In-Reply-To: <1389444465.4733098.1468050201343.JavaMail.zimbra@redhat.com> References: <286619954.4301173.1467934040488.JavaMail.zimbra@redhat.com> <1389444465.4733098.1468050201343.JavaMail.zimbra@redhat.com> Message-ID: Exactly - I'm worried that in a couple of years time, someone will delete that download, or upgrade the REST interface, not realising that the installer is (ab)using it for something else... On 9 July 2016 at 08:43, Denis Golovin wrote: > There is no issue opened for this. Do you mean rest service should support > requests to check T&C's using product-id instead of specific file. > Something similar to > https://developers.redhat.com/download-manager/rest/tc-accepted?productId=cdk > > ----- Original Message ----- >> From: "Pete Muir" >> To: "Denis Golovin" >> Cc: "Pavol Pitonak" , devtools at redhat.com, "Rick Wagner" >> Sent: Friday, July 8, 2016 7:52:30 AM >> Subject: Re: [Devtools] Fix an installer problem with a server-side change? >> >> Do we have an issue to replace this with a proper T&C check that >> doesn't involve the name of a file that might get changed without >> someone understanding the installer depends on it? >> >> On 8 July 2016 at 00:27, Denis Golovin wrote: >> > That is correct answer. This url is only to verify T&C's are signed. >> > >> > ----- Original Message ----- >> >> From: "Pavol Pitonak" >> >> To: "Pete Muir" >> >> Cc: devtools at redhat.com, "Rick Wagner" >> >> Sent: Thursday, July 7, 2016 4:50:19 AM >> >> Subject: Re: [Devtools] Fix an installer problem with a server-side >> >> change? >> >> >> >> It's not installing CDK 2.0.0-beta3 but the one specified in [1]. The >> >> mentioned URL is only used for finding out whether the user provided >> >> correct >> >> username/password and whether he had agreed with T&C. >> >> >> >> [1] >> >> https://github.com/redhat-developer-tooling/developer-platform-install/blob/master/requirements.json#L7 >> >> >> >> On Thu, Jul 7, 2016 at 1:40 PM, Pete Muir < pmuir at redhat.com > wrote: >> >> >> >> >> >> On 6 July 2016 at 20:02, Rick Wagner < rwagner at redhat.com > wrote: >> >> > Hello DevTools, >> >> > >> >> > It seems we have a problem with the current version of the Development >> >> > Suite >> >> > installer. We have at least 2 new customer cases reporting inability to >> >> > install due to the message dialogue "Terms and Conditions for the CDK >> >> > have >> >> > not been signed". >> >> > >> >> > This is concerning because we're also seeing similar activity on >> >> > non-support >> >> > channels. It's also worth noting that not every user that has a problem >> >> > reports it-- some just give up and move on. There is enough volume here >> >> > that we probably should treat this with some urgency. >> >> > >> >> > It seems likely the relevant code (thanks for highlighting this, Alexey) >> >> > is >> >> > below: >> >> > >> >> > ------------------------------------------------- >> >> > >> >> > login() { >> >> > this.authFailed = false; >> >> > this.tandcNotSigned = false; >> >> > >> >> > let req = { >> >> > method: 'GET', >> >> > url: >> >> > ' >> >> > https://developers.redhat.com/download-manager/rest/tc-accepted?downloadURL=/file/cdk-2.0.0-beta3.zip >> >> > ', >> >> > <<<<<<<<<---- returns 'false' when not approved >> >> >> >> I noticed when reading this that this code appears to be downloading >> >> CDK 2.0.0-beta3 which implies that either this is an old version of >> >> the installer, or the installer is installing a very old CDK... >> >> >> >> > headers: { >> >> > 'Authorization': 'Basic ' + this.base64.encode(this.username + ':' + >> >> > this.password) >> >> > } >> >> > }; >> >> > >> >> > this.http(req) >> >> > .then(this.handleHttpSuccess.bind(this)) >> >> > .catch(this.handleHttpFailure.bind(this)); >> >> > } >> >> > >> >> > --------------------------------- >> >> > >> >> > >> >> > So we have users getting denied use of our product. Do we require a >> >> > rebuild >> >> > immediately? Maybe. >> >> > >> >> > How about if we changed the rest service >> >> > ( https://developers.redhat.com/download-manager/rest/tc-accepted ) so >> >> > it >> >> > includes a peak at an override database as well as whatever it's >> >> > currently >> >> > doing now? >> >> > >> >> > In that way, we could have the users pop over to a 'yes, I agree to the >> >> > terms' page to insert an entry into the database. The rest service could >> >> > use something like the provided username as a key to ensure a 'true' is >> >> > returned. >> >> > >> >> > >> >> > Or not. Is there a better way to fix this? >> >> > >> >> > Please consider, we need to fix this sooner rather than later.... >> >> > >> >> > Thanks, >> >> > >> >> > Rick >> >> > >> >> > >> >> > _______________________________________________ >> >> > 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 >> >> >> From cdrage at redhat.com Mon Jul 11 14:03:05 2016 From: cdrage at redhat.com (Charlie Drage) Date: Mon, 11 Jul 2016 10:03:05 -0400 Subject: [Devtools] Creation of projectatomic/nulecule-library Docker Hub file In-Reply-To: <73e96295-5605-1816-48b3-4ac7b945afad@dustymabe.com> References: <20160704182039.GA1@7177a189328f> <73e96295-5605-1816-48b3-4ac7b945afad@dustymabe.com> Message-ID: <20160711140305.GA1@16ba7c193f50> Hey all, Thanks for the input :) Once https://github.com/projectatomic/nulecule-library/pull/97 is merged we can create the docker hub. So without further ado! Feel free to review it and we can finally merge in the index PR and get that up and running for Atomic App! :) On 07/07, Dusty Mabe wrote: > > > On 07/04/2016 02:20 PM, Charlie Drage wrote: > > Hey all, > > > > With the work I've been doing on the `atomicapp index` PR (well, > > picking up on the work that vpavlin did), I require the creation of a > > new Docker image that will contain the `index.yaml` file on > > hub.docker.com/projectatomic > > Might be good to have it be more specific than `index.yaml`. Maybe > nulecule-library-index.yaml > > > > > I have permission for the files, however, I want people's input before > > I add it. > > > > Should the name be `projectatomic/index` or > > `projectatomic/nulecule-library-index` or something of the rather? > > > > PR source: https://github.com/projectatomic/atomicapp/pull/750 > > > > I would prefer: `projectatomic/nulecule-library-index` or just > `projecatomic/nulecule-index` or `projectatomic/nulecule-library`. > > Let's make it happen. > > _______________________________________________ > Devtools mailing list > Devtools at redhat.com > https://www.redhat.com/mailman/listinfo/devtools -- Charlie Drage Red Hat - Dev Tools / Project Atomic PGP - 4096R/C037D617 http://pgp.mit.edu/pks/lookup?op=get&search=0xDA227403C037D617 From rwagner at redhat.com Mon Jul 11 14:20:02 2016 From: rwagner at redhat.com (Rick Wagner) Date: Mon, 11 Jul 2016 09:20:02 -0500 Subject: [Devtools] Development suite installer questions Message-ID: Hello DevTools, We're working with a customer that brings a few interesting questions about the installer. Question 1: When an attempt is made to download the Development Suite, we see the error: "Oops. Something went wrong The download failed. Please check if you have internet access, connected to VPN, have correct configuration for proxy server. Try to download again after problem is fixed." The user tells us they are behind a proxy server. Do we have any specific recommendations for a remedy? Question 2: The same user notes that when they do get the installer, it urges them to install Cygwin even though it's already present. Is there a way to avoid this? Thanks, Rick -------------- next part -------------- An HTML attachment was scrubbed... URL: From ldimaggi at redhat.com Mon Jul 11 15:12:48 2016 From: ldimaggi at redhat.com (Leonard Dimaggio) Date: Mon, 11 Jul 2016 11:12:48 -0400 Subject: [Devtools] Development suite installer questions In-Reply-To: References: Message-ID: Hey Rick, The installer does not currently detect pre-existing/pre-installed instances of Cygwin. See: https://issues.jboss.org/browse/RHDEVDOCS-47 As of today, the installer is able to detect these components: - Java - VirtualBox - Vagrant Not sure about the download issue that you mentioned - are they able to download anything from Red Hat? -- Len On Mon, Jul 11, 2016 at 10:20 AM, Rick Wagner wrote: > Hello DevTools, > > We're working with a customer that brings a few interesting questions > about the installer. > > > Question 1: > > When an attempt is made to download the Development Suite, we see the > error: > > "Oops. Something went wrong > The download failed. Please check if you have internet access, connected > to VPN, have correct configuration for proxy server. Try to download again > after problem is fixed." > > The user tells us they are behind a proxy server. Do we have any specific > recommendations for a remedy? > > > Question 2: > > The same user notes that when they do get the installer, it urges them to > install Cygwin even though it's already present. Is there a way to avoid > this? > > Thanks, > > Rick > > > _______________________________________________ > Devtools mailing list > Devtools at redhat.com > https://www.redhat.com/mailman/listinfo/devtools > > -- Len DiMaggio (ldimaggi at redhat.com) JBoss by Red Hat 314 Littleton Road Westford, MA 01886 USA tel: 978.392.3179 cell: 781.472.9912 http://www.redhat.com http://community.jboss.org/people/ldimaggio -------------- next part -------------- An HTML attachment was scrubbed... URL: From rwagner at redhat.com Mon Jul 11 15:35:29 2016 From: rwagner at redhat.com (Rick Wagner) Date: Mon, 11 Jul 2016 10:35:29 -0500 Subject: [Devtools] Development suite installer questions In-Reply-To: References: Message-ID: Thanks for that note, Len. We have a KCS open for the Cygwin issue, we'll urge users to ignore the superfluous suggestion. We've asked about downloading other items from developers.redhat.com and are pursuing a browser proxy settings remedy for the download problem. (Let's see if that's effective. It looks like some proxy download issues can be solved this way, some cannot. We'll find out what flavor we are.) Rick -------------- next part -------------- An HTML attachment was scrubbed... URL: From omajid at redhat.com Mon Jul 11 19:48:37 2016 From: omajid at redhat.com (Omair Majid) Date: Mon, 11 Jul 2016 15:48:37 -0400 Subject: [Devtools] How do I fix a doc at developers.redhat.com? Message-ID: <20160711194836.GC1485@redhat.com> Hi, I got a request from a few users about a particular doc at http://developers.redhat.com missing some information that they were looking for. What's the process for updating these docs? If it helps, I am looking to update this Getting Started Guide (http://developers.redhat.com/products/dotnet/get-started/) which should document some things that need to be done between the existing steps 2 and 3 as well as 3 and 4. Thanks, Omair -- PGP Key: 66484681 (http://pgp.mit.edu/) Fingerprint = F072 555B 0A17 3957 4E95 0056 F286 F14F 6648 4681 From rwagner at redhat.com Mon Jul 11 20:00:32 2016 From: rwagner at redhat.com (Rick Wagner) Date: Mon, 11 Jul 2016 15:00:32 -0500 Subject: [Devtools] What *is* the 'default Unix socket location' for Docker? Message-ID: Hello DevTools, When working with Developer Studio and the Docker view, setup tells us to establish the initial connection with the 'default Unix socket Location': "Add the relevant socket information for your host. If you are unsure about this step, use the default Unix socket Location value." Unfortunately, the dialogue box calls for navigation to some file location, the user is given no clue what the proper value is. Entering nothing yields a 'ping failed' dialogue and no connection. Can somebody please say what a proper value might be? Thank you, Rick [1] https://access.redhat.com/articles/1488373 [2] http://tools.jboss.org/documentation/howto/docker_basics.html -------------- next part -------------- An HTML attachment was scrubbed... URL: From rwagner at redhat.com Mon Jul 11 20:26:22 2016 From: rwagner at redhat.com (Rick Wagner) Date: Mon, 11 Jul 2016 15:26:22 -0500 Subject: [Devtools] What *is* the 'default Unix socket location' for Docker? In-Reply-To: References: Message-ID: Hi All, Sorry, I probably wasn't specific enough. The use case is using Docker as provided by the CDK. There doesn't seem to be a default provided in the Docker setup dialogue.... Thanks, Rick On Mon, Jul 11, 2016 at 3:00 PM, Rick Wagner wrote: > Hello DevTools, > > When working with Developer Studio and the Docker view, setup tells us to > establish the initial connection with the 'default Unix socket Location': > > "Add the relevant socket information for your host. If you are unsure > about this step, use the default Unix socket Location value." > > Unfortunately, the dialogue box calls for navigation to some file > location, the user is given no clue what the proper value is. Entering > nothing yields a 'ping failed' dialogue and no connection. > > Can somebody please say what a proper value might be? > > Thank you, > > Rick > > [1] https://access.redhat.com/articles/1488373 > [2] http://tools.jboss.org/documentation/howto/docker_basics.html > > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From tmancini at redhat.com Mon Jul 11 20:37:42 2016 From: tmancini at redhat.com (Todd Mancini) Date: Mon, 11 Jul 2016 16:37:42 -0400 Subject: [Devtools] What *is* the 'default Unix socket location' for Docker? In-Reply-To: References: Message-ID: unix:///var/run/docker.sock Although most are running on TCP 2375 On Mon, Jul 11, 2016 at 4:26 PM, Rick Wagner wrote: > Hi All, > > Sorry, I probably wasn't specific enough. > > The use case is using Docker as provided by the CDK. There doesn't seem > to be a default provided in the Docker setup dialogue.... > > Thanks, > > Rick > > > > On Mon, Jul 11, 2016 at 3:00 PM, Rick Wagner wrote: > >> Hello DevTools, >> >> When working with Developer Studio and the Docker view, setup tells us to >> establish the initial connection with the 'default Unix socket Location': >> >> "Add the relevant socket information for your host. If you are unsure >> about this step, use the default Unix socket Location value." >> >> Unfortunately, the dialogue box calls for navigation to some file >> location, the user is given no clue what the proper value is. Entering >> nothing yields a 'ping failed' dialogue and no connection. >> >> Can somebody please say what a proper value might be? >> >> Thank you, >> >> Rick >> >> [1] https://access.redhat.com/articles/1488373 >> [2] http://tools.jboss.org/documentation/howto/docker_basics.html >> >> >> > > _______________________________________________ > 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 Mon Jul 11 20:55:37 2016 From: cdrage at redhat.com (Charlie Drage) Date: Mon, 11 Jul 2016 16:55:37 -0400 Subject: [Devtools] Removal/alternatives of coverage.io from Atomic App Message-ID: <20160711205537.GA1@49367cbbbaf2> Lately it's been nothing but problems with coveralls.io in regards to Atomic App (delays, often 1hour+ for results to come back from them to Git Hub) Does anyone know of any decent alternatives? If not, perhaps we could disable this? -- Charlie Drage Red Hat - Dev Tools / Project Atomic PGP - 4096R/C037D617 http://pgp.mit.edu/pks/lookup?op=get&search=0xDA227403C037D617 From dusty at dustymabe.com Mon Jul 11 21:28:46 2016 From: dusty at dustymabe.com (Dusty Mabe) Date: Mon, 11 Jul 2016 17:28:46 -0400 Subject: [Devtools] How do I fix a doc at developers.redhat.com? In-Reply-To: <20160711194836.GC1485@redhat.com> References: <20160711194836.GC1485@redhat.com> Message-ID: <249ebc0f-6b8b-e84d-cfe9-98a98068e941@dustymabe.com> On 07/11/2016 03:48 PM, Omair Majid wrote: > Hi, > > I got a request from a few users about a particular doc at > http://developers.redhat.com missing some information that they were > looking for. What's the process for updating these docs? > > If it helps, I am looking to update this Getting Started Guide > (http://developers.redhat.com/products/dotnet/get-started/) which should > document some things that need to be done between the existing steps 2 > and 3 as well as 3 and 4. > > Thanks, > Omair Maybe submit a PR to https://github.com/redhat-developer/developers.redhat.com Here is the source for that page I believe: https://github.com/redhat-developer/developers.redhat.com/blob/master/products/dotnet/get-started.adoc Dusty From omajid at redhat.com Mon Jul 11 21:33:15 2016 From: omajid at redhat.com (Omair Majid) Date: Mon, 11 Jul 2016 17:33:15 -0400 Subject: [Devtools] How do I fix a doc at developers.redhat.com? In-Reply-To: <249ebc0f-6b8b-e84d-cfe9-98a98068e941@dustymabe.com> References: <20160711194836.GC1485@redhat.com> <249ebc0f-6b8b-e84d-cfe9-98a98068e941@dustymabe.com> Message-ID: <20160711213315.GD4079@redhat.com> * Dusty Mabe [2016-07-11 17:28]: > Maybe submit a PR to > https://github.com/redhat-developer/developers.redhat.com > > Here is the source for that page I believe: > https://github.com/redhat-developer/developers.redhat.com/blob/master/products/dotnet/get-started.adoc Thanks! Omair -- PGP Key: 66484681 (http://pgp.mit.edu/) Fingerprint = F072 555B 0A17 3957 4E95 0056 F286 F14F 6648 4681 From jporter at redhat.com Mon Jul 11 21:34:33 2016 From: jporter at redhat.com (Jason Porter) Date: Mon, 11 Jul 2016 15:34:33 -0600 Subject: [Devtools] How do I fix a doc at developers.redhat.com? In-Reply-To: <20160711213315.GD4079@redhat.com> References: <20160711194836.GC1485@redhat.com> <249ebc0f-6b8b-e84d-cfe9-98a98068e941@dustymabe.com> <20160711213315.GD4079@redhat.com> Message-ID: That's exactly how you do it. If you get stuck, feel free to reach out to redhat-developers-web at redhat.com On Mon, Jul 11, 2016 at 3:33 PM, Omair Majid wrote: > * Dusty Mabe [2016-07-11 17:28]: > > Maybe submit a PR to > > https://github.com/redhat-developer/developers.redhat.com > > > > Here is the source for that page I believe: > > > https://github.com/redhat-developer/developers.redhat.com/blob/master/products/dotnet/get-started.adoc > > Thanks! > > Omair > > -- > PGP Key: 66484681 (http://pgp.mit.edu/) > Fingerprint = F072 555B 0A17 3957 4E95 0056 F286 F14F 6648 4681 > > _______________________________________________ > Devtools mailing list > Devtools at redhat.com > https://www.redhat.com/mailman/listinfo/devtools > -- Jason Porter Senior Software Engineer developers.redhat.com -------------- next part -------------- An HTML attachment was scrubbed... URL: From prkumar at redhat.com Tue Jul 12 03:45:07 2016 From: prkumar at redhat.com (Praveen Kumar) Date: Tue, 12 Jul 2016 09:15:07 +0530 Subject: [Devtools] What *is* the 'default Unix socket location' for Docker? In-Reply-To: References: Message-ID: On Tue, Jul 12, 2016 at 1:56 AM, Rick Wagner wrote: > Hi All, > > Sorry, I probably wasn't specific enough. > > The use case is using Docker as provided by the CDK. There doesn't seem to > be a default provided in the Docker setup dialogue.... > Docker daemon in CDK is running on default unix socket and also TCP one. Below is the docker daemon options which is running for CDK. /usr/bin/docker-current daemon --selinux-enabled -H tcp://0.0.0.0:2376 \ => TCP Socket -H unix:///var/run/docker.sock \ => Unix Socket --tlscacert=/etc/docker/ca.pem \ --tlscert=/etc/docker/server-cert.pem \ --tlskey=/etc/docker/server-key.pem \ --tlsverify --storage-driver devicemapper \ --storage-opt dm.fs=xfs \ --storage-opt dm.thinpooldev=/dev/mapper/VolGroup00-docker--pool \ --storage-opt dm.use_deferred_removal=true \ --storage-opt dm.use_deferred_deletion=true \ --add-registry registry.access.redhat.com And port it listening '2376'. Proto Recv-Q Send-Q Local Address Foreign Address State PID/Program name tcp 0 0 0.0.0.0:22 0.0.0.0:* LISTEN 921/sshd tcp6 0 0 :::2376 :::* LISTEN 12631/docker-curren tcp6 0 0 :::22 :::* LISTEN 921/sshd -- Praveen Kumar https://fedoraproject.org/wiki/User:Kumarpraveen From degolovi at redhat.com Tue Jul 12 05:09:35 2016 From: degolovi at redhat.com (Denis Golovin) Date: Tue, 12 Jul 2016 01:09:35 -0400 (EDT) Subject: [Devtools] Development suite installer questions In-Reply-To: References: Message-ID: <1398019809.5131103.1468300175128.JavaMail.zimbra@redhat.com> Rick, see my comments inline ----- Original Message ----- > From: "Rick Wagner" > To: devtools at redhat.com > Sent: Monday, July 11, 2016 7:20:02 AM > Subject: [Devtools] Development suite installer questions > > Hello DevTools, > > We're working with a customer that brings a few interesting questions about > the installer. > > > Question 1: > > When an attempt is made to download the Development Suite, we see the error: > > "Oops. Something went wrong > The download failed. Please check if you have internet access, connected to > VPN, have correct configuration for proxy server. Try to download again > after problem is fixed." > > The user tells us they are behind a proxy server. Do we have any specific > recommendations for a remedy? I see first problem here is that message doesn't say what exactly went wrong and what installer was trying to download. It could be proxy issue related to: 1. User-Agent header does not set it at all; 2. Download for Vagrant and Oracle Virtualbox uses redirects on developers.redhat.com not direct links see details here https://issues.jboss.org/browse/ORG-2929. Could you ask if links http://developers.stage.redhat.com/redirect/to/virtualbox-5.0.8.download http://developers.stage.redhat.com/redirect/to/vagrant-1.7.4.download work from browser? > > > Question 2: > > The same user notes that when they do get the installer, it urges them to > install Cygwin even though it's already present. Is there a way to avoid > this? Cygwin detection is not implemented yet and it might become optional component to install soon, see supported terminals discussion. Thanks, Denis > > Thanks, > > Rick > > > _______________________________________________ > Devtools mailing list > Devtools at redhat.com > https://www.redhat.com/mailman/listinfo/devtools > From pmuir at redhat.com Tue Jul 12 05:38:38 2016 From: pmuir at redhat.com (Pete Muir) Date: Tue, 12 Jul 2016 06:38:38 +0100 Subject: [Devtools] What *is* the 'default Unix socket location' for Docker? In-Reply-To: References: Message-ID: tcp://10.1.2.2:2375 But development suite should set this up for you automatically. If it doesn't, file a bug :-) On 11 July 2016 at 21:00, Rick Wagner wrote: > Hello DevTools, > > When working with Developer Studio and the Docker view, setup tells us to > establish the initial connection with the 'default Unix socket Location': > > "Add the relevant socket information for your host. If you are unsure about > this step, use the default Unix socket Location value." > > Unfortunately, the dialogue box calls for navigation to some file location, > the user is given no clue what the proper value is. Entering nothing yields > a 'ping failed' dialogue and no connection. > > Can somebody please say what a proper value might be? > > Thank you, > > Rick > > [1] https://access.redhat.com/articles/1488373 > [2] http://tools.jboss.org/documentation/howto/docker_basics.html > > > > _______________________________________________ > Devtools mailing list > Devtools at redhat.com > https://www.redhat.com/mailman/listinfo/devtools > From prkumar at redhat.com Tue Jul 12 05:55:45 2016 From: prkumar at redhat.com (Praveen Kumar) Date: Tue, 12 Jul 2016 11:25:45 +0530 Subject: [Devtools] What *is* the 'default Unix socket location' for Docker? In-Reply-To: References: Message-ID: On Tue, Jul 12, 2016 at 11:08 AM, Pete Muir wrote: > tcp://10.1.2.2:2375 Pete, I think development suite get those details (docker env to connect external tooling) from vagrant service manager. $ vagrant service-manager env docker # Set the following environment variables to enable access to the # docker daemon running inside of the vagrant virtual machine: export DOCKER_HOST=tcp://10.1.2.2:2376 So port should be 2376 instead '2375' or I have wrong assumption? > > But development suite should set this up for you automatically. If it > doesn't, file a bug :-) -- Praveen Kumar https://fedoraproject.org/wiki/User:Kumarpraveen From degolovi at redhat.com Tue Jul 12 06:05:19 2016 From: degolovi at redhat.com (Denis Golovin) Date: Tue, 12 Jul 2016 02:05:19 -0400 (EDT) Subject: [Devtools] What *is* the 'default Unix socket location' for Docker? In-Reply-To: References: Message-ID: <1739477495.5136514.1468303519660.JavaMail.zimbra@redhat.com> This is done on DevStudio side. DevSuite just configures runtime detection, so CDK appears in servers view and set required env variables to avoid additional usrname/password request. Denis ----- Original Message ----- > From: "Praveen Kumar" > To: "Pete Muir" > Cc: devtools at redhat.com, "Rick Wagner" > Sent: Monday, July 11, 2016 10:55:45 PM > Subject: Re: [Devtools] What *is* the 'default Unix socket location' for Docker? > > On Tue, Jul 12, 2016 at 11:08 AM, Pete Muir wrote: > > tcp://10.1.2.2:2375 > > Pete, I think development suite get those details (docker env to > connect external tooling) from vagrant service manager. > > $ vagrant service-manager env docker > # Set the following environment variables to enable access to the > # docker daemon running inside of the vagrant virtual machine: > export DOCKER_HOST=tcp://10.1.2.2:2376 > > So port should be 2376 instead '2375' or I have wrong assumption? > > > > > But development suite should set this up for you automatically. If it > > doesn't, file a bug :-) > > -- > Praveen Kumar > https://fedoraproject.org/wiki/User:Kumarpraveen > > _______________________________________________ > Devtools mailing list > Devtools at redhat.com > https://www.redhat.com/mailman/listinfo/devtools > From degolovi at redhat.com Tue Jul 12 06:31:06 2016 From: degolovi at redhat.com (Denis Golovin) Date: Tue, 12 Jul 2016 02:31:06 -0400 (EDT) Subject: [Devtools] Fix an installer problem with a server-side change? In-Reply-To: References: <286619954.4301173.1467934040488.JavaMail.zimbra@redhat.com> <1389444465.4733098.1468050201343.JavaMail.zimbra@redhat.com> Message-ID: <1208091986.5139288.1468305066328.JavaMail.zimbra@redhat.com> Pete, it seems T&C's workflow is really simple now, T&C's just signed when registrations is done. It seems that this request could be just https://developers.redhat.com/download-manager/rest/tc-accepted without any additional parameters. Who should I discuss it with? Is David Hladky right person? Thanks, Denis ----- Original Message ----- > From: "Pete Muir" > To: "Denis Golovin" > Cc: "Pavol Pitonak" , devtools at redhat.com, "Rick Wagner" > Sent: Monday, July 11, 2016 4:32:56 AM > Subject: Re: [Devtools] Fix an installer problem with a server-side change? > > Exactly - I'm worried that in a couple of years time, someone will > delete that download, or upgrade the REST interface, not realising > that the installer is (ab)using it for something else... > > On 9 July 2016 at 08:43, Denis Golovin wrote: > > There is no issue opened for this. Do you mean rest service should support > > requests to check T&C's using product-id instead of specific file. > > Something similar to > > https://developers.redhat.com/download-manager/rest/tc-accepted?productId=cdk > > > > ----- Original Message ----- > >> From: "Pete Muir" > >> To: "Denis Golovin" > >> Cc: "Pavol Pitonak" , devtools at redhat.com, "Rick > >> Wagner" > >> Sent: Friday, July 8, 2016 7:52:30 AM > >> Subject: Re: [Devtools] Fix an installer problem with a server-side > >> change? > >> > >> Do we have an issue to replace this with a proper T&C check that > >> doesn't involve the name of a file that might get changed without > >> someone understanding the installer depends on it? > >> > >> On 8 July 2016 at 00:27, Denis Golovin wrote: > >> > That is correct answer. This url is only to verify T&C's are signed. > >> > > >> > ----- Original Message ----- > >> >> From: "Pavol Pitonak" > >> >> To: "Pete Muir" > >> >> Cc: devtools at redhat.com, "Rick Wagner" > >> >> Sent: Thursday, July 7, 2016 4:50:19 AM > >> >> Subject: Re: [Devtools] Fix an installer problem with a server-side > >> >> change? > >> >> > >> >> It's not installing CDK 2.0.0-beta3 but the one specified in [1]. The > >> >> mentioned URL is only used for finding out whether the user provided > >> >> correct > >> >> username/password and whether he had agreed with T&C. > >> >> > >> >> [1] > >> >> https://github.com/redhat-developer-tooling/developer-platform-install/blob/master/requirements.json#L7 > >> >> > >> >> On Thu, Jul 7, 2016 at 1:40 PM, Pete Muir < pmuir at redhat.com > wrote: > >> >> > >> >> > >> >> On 6 July 2016 at 20:02, Rick Wagner < rwagner at redhat.com > wrote: > >> >> > Hello DevTools, > >> >> > > >> >> > It seems we have a problem with the current version of the > >> >> > Development > >> >> > Suite > >> >> > installer. We have at least 2 new customer cases reporting inability > >> >> > to > >> >> > install due to the message dialogue "Terms and Conditions for the CDK > >> >> > have > >> >> > not been signed". > >> >> > > >> >> > This is concerning because we're also seeing similar activity on > >> >> > non-support > >> >> > channels. It's also worth noting that not every user that has a > >> >> > problem > >> >> > reports it-- some just give up and move on. There is enough volume > >> >> > here > >> >> > that we probably should treat this with some urgency. > >> >> > > >> >> > It seems likely the relevant code (thanks for highlighting this, > >> >> > Alexey) > >> >> > is > >> >> > below: > >> >> > > >> >> > ------------------------------------------------- > >> >> > > >> >> > login() { > >> >> > this.authFailed = false; > >> >> > this.tandcNotSigned = false; > >> >> > > >> >> > let req = { > >> >> > method: 'GET', > >> >> > url: > >> >> > ' > >> >> > https://developers.redhat.com/download-manager/rest/tc-accepted?downloadURL=/file/cdk-2.0.0-beta3.zip > >> >> > ', > >> >> > <<<<<<<<<---- returns 'false' when not approved > >> >> > >> >> I noticed when reading this that this code appears to be downloading > >> >> CDK 2.0.0-beta3 which implies that either this is an old version of > >> >> the installer, or the installer is installing a very old CDK... > >> >> > >> >> > headers: { > >> >> > 'Authorization': 'Basic ' + this.base64.encode(this.username + ':' + > >> >> > this.password) > >> >> > } > >> >> > }; > >> >> > > >> >> > this.http(req) > >> >> > .then(this.handleHttpSuccess.bind(this)) > >> >> > .catch(this.handleHttpFailure.bind(this)); > >> >> > } > >> >> > > >> >> > --------------------------------- > >> >> > > >> >> > > >> >> > So we have users getting denied use of our product. Do we require a > >> >> > rebuild > >> >> > immediately? Maybe. > >> >> > > >> >> > How about if we changed the rest service > >> >> > ( https://developers.redhat.com/download-manager/rest/tc-accepted ) > >> >> > so > >> >> > it > >> >> > includes a peak at an override database as well as whatever it's > >> >> > currently > >> >> > doing now? > >> >> > > >> >> > In that way, we could have the users pop over to a 'yes, I agree to > >> >> > the > >> >> > terms' page to insert an entry into the database. The rest service > >> >> > could > >> >> > use something like the provided username as a key to ensure a 'true' > >> >> > is > >> >> > returned. > >> >> > > >> >> > > >> >> > Or not. Is there a better way to fix this? > >> >> > > >> >> > Please consider, we need to fix this sooner rather than later.... > >> >> > > >> >> > Thanks, > >> >> > > >> >> > Rick > >> >> > > >> >> > > >> >> > _______________________________________________ > >> >> > 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 > >> >> > >> > From pmuir at redhat.com Tue Jul 12 07:23:39 2016 From: pmuir at redhat.com (Pete Muir) Date: Tue, 12 Jul 2016 08:23:39 +0100 Subject: [Devtools] Fix an installer problem with a server-side change? In-Reply-To: <1208091986.5139288.1468305066328.JavaMail.zimbra@redhat.com> References: <286619954.4301173.1467934040488.JavaMail.zimbra@redhat.com> <1389444465.4733098.1468050201343.JavaMail.zimbra@redhat.com> <1208091986.5139288.1468305066328.JavaMail.zimbra@redhat.com> Message-ID: David H and mark N are the right people. On 12 Jul 2016 7:31 a.m., "Denis Golovin" wrote: > Pete, > > it seems T&C's workflow is really simple now, T&C's just signed > when registrations is done. It seems that this request could be > just https://developers.redhat.com/download-manager/rest/tc-accepted > without any additional parameters. > > Who should I discuss it with? Is David Hladky right person? > > Thanks, > Denis > > ----- Original Message ----- > > From: "Pete Muir" > > To: "Denis Golovin" > > Cc: "Pavol Pitonak" , devtools at redhat.com, "Rick > Wagner" > > Sent: Monday, July 11, 2016 4:32:56 AM > > Subject: Re: [Devtools] Fix an installer problem with a server-side > change? > > > > Exactly - I'm worried that in a couple of years time, someone will > > delete that download, or upgrade the REST interface, not realising > > that the installer is (ab)using it for something else... > > > > On 9 July 2016 at 08:43, Denis Golovin wrote: > > > There is no issue opened for this. Do you mean rest service should > support > > > requests to check T&C's using product-id instead of specific file. > > > Something similar to > > > > https://developers.redhat.com/download-manager/rest/tc-accepted?productId=cdk > > > > > > ----- Original Message ----- > > >> From: "Pete Muir" > > >> To: "Denis Golovin" > > >> Cc: "Pavol Pitonak" , devtools at redhat.com, "Rick > > >> Wagner" > > >> Sent: Friday, July 8, 2016 7:52:30 AM > > >> Subject: Re: [Devtools] Fix an installer problem with a server-side > > >> change? > > >> > > >> Do we have an issue to replace this with a proper T&C check that > > >> doesn't involve the name of a file that might get changed without > > >> someone understanding the installer depends on it? > > >> > > >> On 8 July 2016 at 00:27, Denis Golovin wrote: > > >> > That is correct answer. This url is only to verify T&C's are signed. > > >> > > > >> > ----- Original Message ----- > > >> >> From: "Pavol Pitonak" > > >> >> To: "Pete Muir" > > >> >> Cc: devtools at redhat.com, "Rick Wagner" > > >> >> Sent: Thursday, July 7, 2016 4:50:19 AM > > >> >> Subject: Re: [Devtools] Fix an installer problem with a server-side > > >> >> change? > > >> >> > > >> >> It's not installing CDK 2.0.0-beta3 but the one specified in [1]. > The > > >> >> mentioned URL is only used for finding out whether the user > provided > > >> >> correct > > >> >> username/password and whether he had agreed with T&C. > > >> >> > > >> >> [1] > > >> >> > https://github.com/redhat-developer-tooling/developer-platform-install/blob/master/requirements.json#L7 > > >> >> > > >> >> On Thu, Jul 7, 2016 at 1:40 PM, Pete Muir < pmuir at redhat.com > > wrote: > > >> >> > > >> >> > > >> >> On 6 July 2016 at 20:02, Rick Wagner < rwagner at redhat.com > wrote: > > >> >> > Hello DevTools, > > >> >> > > > >> >> > It seems we have a problem with the current version of the > > >> >> > Development > > >> >> > Suite > > >> >> > installer. We have at least 2 new customer cases reporting > inability > > >> >> > to > > >> >> > install due to the message dialogue "Terms and Conditions for > the CDK > > >> >> > have > > >> >> > not been signed". > > >> >> > > > >> >> > This is concerning because we're also seeing similar activity on > > >> >> > non-support > > >> >> > channels. It's also worth noting that not every user that has a > > >> >> > problem > > >> >> > reports it-- some just give up and move on. There is enough > volume > > >> >> > here > > >> >> > that we probably should treat this with some urgency. > > >> >> > > > >> >> > It seems likely the relevant code (thanks for highlighting this, > > >> >> > Alexey) > > >> >> > is > > >> >> > below: > > >> >> > > > >> >> > ------------------------------------------------- > > >> >> > > > >> >> > login() { > > >> >> > this.authFailed = false; > > >> >> > this.tandcNotSigned = false; > > >> >> > > > >> >> > let req = { > > >> >> > method: 'GET', > > >> >> > url: > > >> >> > ' > > >> >> > > https://developers.redhat.com/download-manager/rest/tc-accepted?downloadURL=/file/cdk-2.0.0-beta3.zip > > >> >> > ', > > >> >> > <<<<<<<<<---- returns 'false' when not approved > > >> >> > > >> >> I noticed when reading this that this code appears to be > downloading > > >> >> CDK 2.0.0-beta3 which implies that either this is an old version of > > >> >> the installer, or the installer is installing a very old CDK... > > >> >> > > >> >> > headers: { > > >> >> > 'Authorization': 'Basic ' + this.base64.encode(this.username + > ':' + > > >> >> > this.password) > > >> >> > } > > >> >> > }; > > >> >> > > > >> >> > this.http(req) > > >> >> > .then(this.handleHttpSuccess.bind(this)) > > >> >> > .catch(this.handleHttpFailure.bind(this)); > > >> >> > } > > >> >> > > > >> >> > --------------------------------- > > >> >> > > > >> >> > > > >> >> > So we have users getting denied use of our product. Do we > require a > > >> >> > rebuild > > >> >> > immediately? Maybe. > > >> >> > > > >> >> > How about if we changed the rest service > > >> >> > ( > https://developers.redhat.com/download-manager/rest/tc-accepted ) > > >> >> > so > > >> >> > it > > >> >> > includes a peak at an override database as well as whatever it's > > >> >> > currently > > >> >> > doing now? > > >> >> > > > >> >> > In that way, we could have the users pop over to a 'yes, I agree > to > > >> >> > the > > >> >> > terms' page to insert an entry into the database. The rest > service > > >> >> > could > > >> >> > use something like the provided username as a key to ensure a > 'true' > > >> >> > is > > >> >> > returned. > > >> >> > > > >> >> > > > >> >> > Or not. Is there a better way to fix this? > > >> >> > > > >> >> > Please consider, we need to fix this sooner rather than later.... > > >> >> > > > >> >> > Thanks, > > >> >> > > > >> >> > Rick > > >> >> > > > >> >> > > > >> >> > _______________________________________________ > > >> >> > 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 jmaury at redhat.com Tue Jul 12 07:23:26 2016 From: jmaury at redhat.com (Jean-Francois Maury) Date: Tue, 12 Jul 2016 09:23:26 +0200 Subject: [Devtools] What *is* the 'default Unix socket location' for Docker? In-Reply-To: <1739477495.5136514.1468303519660.JavaMail.zimbra@redhat.com> References: <1739477495.5136514.1468303519660.JavaMail.zimbra@redhat.com> Message-ID: And from the server view, you can just click 'Show In -> Docker Explorer' and it wil create the docker connection for you. Jeff On Tue, Jul 12, 2016 at 8:05 AM, Denis Golovin wrote: > This is done on DevStudio side. DevSuite just configures runtime > detection, so > CDK appears in servers view and set required env variables to avoid > additional > usrname/password request. > > > Denis > > ----- Original Message ----- > > From: "Praveen Kumar" > > To: "Pete Muir" > > Cc: devtools at redhat.com, "Rick Wagner" > > Sent: Monday, July 11, 2016 10:55:45 PM > > Subject: Re: [Devtools] What *is* the 'default Unix socket location' > for Docker? > > > > On Tue, Jul 12, 2016 at 11:08 AM, Pete Muir wrote: > > > tcp://10.1.2.2:2375 > > > > Pete, I think development suite get those details (docker env to > > connect external tooling) from vagrant service manager. > > > > $ vagrant service-manager env docker > > # Set the following environment variables to enable access to the > > # docker daemon running inside of the vagrant virtual machine: > > export DOCKER_HOST=tcp://10.1.2.2:2376 > > > > So port should be 2376 instead '2375' or I have wrong assumption? > > > > > > > > But development suite should set this up for you automatically. If it > > > doesn't, file a bug :-) > > > > -- > > Praveen Kumar > > https://fedoraproject.org/wiki/User:Kumarpraveen > > > > _______________________________________________ > > 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 pmuir at redhat.com Tue Jul 12 07:38:23 2016 From: pmuir at redhat.com (Pete Muir) Date: Tue, 12 Jul 2016 08:38:23 +0100 Subject: [Devtools] What *is* the 'default Unix socket location' for Docker? In-Reply-To: References: Message-ID: No, that's correct. Sorry! On 12 Jul 2016 6:55 a.m., "Praveen Kumar" wrote: > On Tue, Jul 12, 2016 at 11:08 AM, Pete Muir wrote: > > tcp://10.1.2.2:2375 > > Pete, I think development suite get those details (docker env to > connect external tooling) from vagrant service manager. > > $ vagrant service-manager env docker > # Set the following environment variables to enable access to the > # docker daemon running inside of the vagrant virtual machine: > export DOCKER_HOST=tcp://10.1.2.2:2376 > > So port should be 2376 instead '2375' or I have wrong assumption? > > > > > But development suite should set this up for you automatically. If it > > doesn't, file a bug :-) > > -- > Praveen Kumar > https://fedoraproject.org/wiki/User:Kumarpraveen > -------------- next part -------------- An HTML attachment was scrubbed... URL: From pmuir at redhat.com Tue Jul 12 09:04:59 2016 From: pmuir at redhat.com (Pete Muir) Date: Tue, 12 Jul 2016 10:04:59 +0100 Subject: [Devtools] What *is* the 'default Unix socket location' for Docker? In-Reply-To: References: <1739477495.5136514.1468303519660.JavaMail.zimbra@redhat.com> Message-ID: That works. I'm not sure it's that intuitive though. It would be nice to be able to go in via the Docker explorer as well... On 12 Jul 2016 8:23 a.m., "Jean-Francois Maury" wrote: > And from the server view, you can just click 'Show In -> Docker Explorer' > and it wil create the docker connection for you. > > Jeff > > On Tue, Jul 12, 2016 at 8:05 AM, Denis Golovin > wrote: > >> This is done on DevStudio side. DevSuite just configures runtime >> detection, so >> CDK appears in servers view and set required env variables to avoid >> additional >> usrname/password request. >> >> >> Denis >> >> ----- Original Message ----- >> > From: "Praveen Kumar" >> > To: "Pete Muir" >> > Cc: devtools at redhat.com, "Rick Wagner" >> > Sent: Monday, July 11, 2016 10:55:45 PM >> > Subject: Re: [Devtools] What *is* the 'default Unix socket location' >> for Docker? >> > >> > On Tue, Jul 12, 2016 at 11:08 AM, Pete Muir wrote: >> > > tcp://10.1.2.2:2375 >> > >> > Pete, I think development suite get those details (docker env to >> > connect external tooling) from vagrant service manager. >> > >> > $ vagrant service-manager env docker >> > # Set the following environment variables to enable access to the >> > # docker daemon running inside of the vagrant virtual machine: >> > export DOCKER_HOST=tcp://10.1.2.2:2376 >> > >> > So port should be 2376 instead '2375' or I have wrong assumption? >> > >> > > >> > > But development suite should set this up for you automatically. If it >> > > doesn't, file a bug :-) >> > >> > -- >> > Praveen Kumar >> > https://fedoraproject.org/wiki/User:Kumarpraveen >> > >> > _______________________________________________ >> > 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 mmalina at redhat.com Tue Jul 12 09:22:35 2016 From: mmalina at redhat.com (Martin Malina) Date: Tue, 12 Jul 2016 11:22:35 +0200 Subject: [Devtools] What *is* the 'default Unix socket location' for Docker? In-Reply-To: References: <1739477495.5136514.1468303519660.JavaMail.zimbra@redhat.com> Message-ID: That works also - when you start CDK in devstudio, once started, both openshift and docker connections will get created in OpenShift Explorer and Docker Explorer, respectively. -Martin > On 12. 7. 2016, at 11:04, Pete Muir wrote: > > That works. I'm not sure it's that intuitive though. It would be nice to be able to go in via the Docker explorer as well... > > On 12 Jul 2016 8:23 a.m., "Jean-Francois Maury" > wrote: > And from the server view, you can just click 'Show In -> Docker Explorer' and it wil create the docker connection for you. > > Jeff > > On Tue, Jul 12, 2016 at 8:05 AM, Denis Golovin > wrote: > This is done on DevStudio side. DevSuite just configures runtime detection, so > CDK appears in servers view and set required env variables to avoid additional > usrname/password request. > > > Denis > > ----- Original Message ----- > > From: "Praveen Kumar" > > > To: "Pete Muir" > > > Cc: devtools at redhat.com , "Rick Wagner" > > > Sent: Monday, July 11, 2016 10:55:45 PM > > Subject: Re: [Devtools] What *is* the 'default Unix socket location' for Docker? > > > > On Tue, Jul 12, 2016 at 11:08 AM, Pete Muir > wrote: > > > tcp://10.1.2.2:2375 > > > > Pete, I think development suite get those details (docker env to > > connect external tooling) from vagrant service manager. > > > > $ vagrant service-manager env docker > > # Set the following environment variables to enable access to the > > # docker daemon running inside of the vagrant virtual machine: > > export DOCKER_HOST=tcp://10.1.2.2:2376 > > > > So port should be 2376 instead '2375' or I have wrong assumption? > > > > > > > > But development suite should set this up for you automatically. If it > > > doesn't, file a bug :-) > > > > -- > > Praveen Kumar > > https://fedoraproject.org/wiki/User:Kumarpraveen > > > > _______________________________________________ > > 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 hferents at redhat.com Tue Jul 12 09:27:45 2016 From: hferents at redhat.com (Hardy Ferentschik) Date: Tue, 12 Jul 2016 11:27:45 +0200 Subject: [Devtools] What *is* the 'default Unix socket location' for Docker? In-Reply-To: References: Message-ID: <20160712092745.GC56230@nineveh.local> Hi, On Tue, 12-Jul-2016 11:25, Praveen Kumar wrote: > On Tue, Jul 12, 2016 at 11:08 AM, Pete Muir wrote: > > tcp://10.1.2.2:2375 > > Pete, I think development suite get those details (docker env to > connect external tooling) from vagrant service manager. +1 Also my understanding. There should really nothing be to be configured. It might be that the CDK did not boot/start correctly or something else went wrong. Would be interesting to know whether the CDK is up and running and whether 'vagrant service-manager env' returns the DOCKER settings. --Hardy -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 496 bytes Desc: not available URL: From rwagner at redhat.com Tue Jul 12 13:09:20 2016 From: rwagner at redhat.com (Rick Wagner) Date: Tue, 12 Jul 2016 08:09:20 -0500 Subject: [Devtools] Development suite installer questions In-Reply-To: <1398019809.5131103.1468300175128.JavaMail.zimbra@redhat.com> References: <1398019809.5131103.1468300175128.JavaMail.zimbra@redhat.com> Message-ID: Thanks much for that advice, Denis. We'll work with the customer to see if this can be used with the browser 'whitelist' to enable use of the Development Suite. Rick On Tue, Jul 12, 2016 at 12:09 AM, Denis Golovin wrote: > Rick, > > see my comments inline > > ----- Original Message ----- > > From: "Rick Wagner" > > To: devtools at redhat.com > > Sent: Monday, July 11, 2016 7:20:02 AM > > Subject: [Devtools] Development suite installer questions > > > > Hello DevTools, > > > > We're working with a customer that brings a few interesting questions > about > > the installer. > > > > > > Question 1: > > > > When an attempt is made to download the Development Suite, we see the > error: > > > > "Oops. Something went wrong > > The download failed. Please check if you have internet access, connected > to > > VPN, have correct configuration for proxy server. Try to download again > > after problem is fixed." > > > > The user tells us they are behind a proxy server. Do we have any specific > > recommendations for a remedy? > > I see first problem here is that message doesn't say what exactly went > wrong and what installer was trying to download. > > It could be proxy issue related to: > 1. User-Agent header does not set it at all; > 2. Download for Vagrant and Oracle Virtualbox uses redirects on > developers.redhat.com not direct links see > details here https://issues.jboss.org/browse/ORG-2929. > > Could you ask if links > > http://developers.stage.redhat.com/redirect/to/virtualbox-5.0.8.download > http://developers.stage.redhat.com/redirect/to/vagrant-1.7.4.download > > work from browser? > > > > > > > Question 2: > > > > The same user notes that when they do get the installer, it urges them to > > install Cygwin even though it's already present. Is there a way to avoid > > this? > > Cygwin detection is not implemented yet and it might become optional > component to install soon, see supported terminals discussion. > > Thanks, > Denis > > > > > Thanks, > > > > Rick > > > > > > _______________________________________________ > > Devtools mailing list > > Devtools at redhat.com > > https://www.redhat.com/mailman/listinfo/devtools > > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From rwagner at redhat.com Tue Jul 12 15:31:37 2016 From: rwagner at redhat.com (Rick Wagner) Date: Tue, 12 Jul 2016 10:31:37 -0500 Subject: [Devtools] What *is* the 'default Unix socket location' for Docker? In-Reply-To: <20160712092745.GC56230@nineveh.local> References: <20160712092745.GC56230@nineveh.local> Message-ID: Hello All, Many thanks for these great tips, the Development Suite has performed flawlessly. (The fault was mine. I didn't use the 'Servers' view to start the CDK and went off to manipulate it from the command line. When I used the Developer Studio provided tools, everything just worked.) Thanks, Rick On Tue, Jul 12, 2016 at 4:27 AM, Hardy Ferentschik wrote: > Hi, > > On Tue, 12-Jul-2016 11:25, Praveen Kumar wrote: > > On Tue, Jul 12, 2016 at 11:08 AM, Pete Muir wrote: > > > tcp://10.1.2.2:2375 > > > > Pete, I think development suite get those details (docker env to > > connect external tooling) from vagrant service manager. > > +1 Also my understanding. There should really nothing be to be configured. > It might be that the CDK did not boot/start correctly or something else > went > wrong. Would be interesting to know whether the CDK is up and running and > whether 'vagrant service-manager env' returns the DOCKER settings. > > --Hardy > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From rstryker at redhat.com Tue Jul 12 18:02:01 2016 From: rstryker at redhat.com (Robert Stryker) Date: Tue, 12 Jul 2016 14:02:01 -0400 Subject: [Devtools] Fix an installer problem with a server-side change? In-Reply-To: References: <286619954.4301173.1467934040488.JavaMail.zimbra@redhat.com> <1389444465.4733098.1468050201343.JavaMail.zimbra@redhat.com> <1208091986.5139288.1468305066328.JavaMail.zimbra@redhat.com> Message-ID: If you find it hard to reach him, you can also check some of the code in jbosstools-base, specifically in 'runtimes' folder. We have some code there that checks whether we have permissions for a given file, which basically means is the t&c accepted. Check in DownloadManagerWorkflowUtility for some parts. getWorkflowStatus is one method that may provide code for you to copy. But there may be newer or cleaner code from David Hladky... - Rob Stryker On Tue, Jul 12, 2016 at 3:23 AM, Pete Muir wrote: > David H and mark N are the right people. > On 12 Jul 2016 7:31 a.m., "Denis Golovin" wrote: > >> Pete, >> >> it seems T&C's workflow is really simple now, T&C's just signed >> when registrations is done. It seems that this request could be >> just https://developers.redhat.com/download-manager/rest/tc-accepted >> without any additional parameters. >> >> Who should I discuss it with? Is David Hladky right person? >> >> Thanks, >> Denis >> >> ----- Original Message ----- >> > From: "Pete Muir" >> > To: "Denis Golovin" >> > Cc: "Pavol Pitonak" , devtools at redhat.com, "Rick >> Wagner" >> > Sent: Monday, July 11, 2016 4:32:56 AM >> > Subject: Re: [Devtools] Fix an installer problem with a server-side >> change? >> > >> > Exactly - I'm worried that in a couple of years time, someone will >> > delete that download, or upgrade the REST interface, not realising >> > that the installer is (ab)using it for something else... >> > >> > On 9 July 2016 at 08:43, Denis Golovin wrote: >> > > There is no issue opened for this. Do you mean rest service should >> support >> > > requests to check T&C's using product-id instead of specific file. >> > > Something similar to >> > > >> https://developers.redhat.com/download-manager/rest/tc-accepted?productId=cdk >> > > >> > > ----- Original Message ----- >> > >> From: "Pete Muir" >> > >> To: "Denis Golovin" >> > >> Cc: "Pavol Pitonak" , devtools at redhat.com, >> "Rick >> > >> Wagner" >> > >> Sent: Friday, July 8, 2016 7:52:30 AM >> > >> Subject: Re: [Devtools] Fix an installer problem with a server-side >> > >> change? >> > >> >> > >> Do we have an issue to replace this with a proper T&C check that >> > >> doesn't involve the name of a file that might get changed without >> > >> someone understanding the installer depends on it? >> > >> >> > >> On 8 July 2016 at 00:27, Denis Golovin wrote: >> > >> > That is correct answer. This url is only to verify T&C's are >> signed. >> > >> > >> > >> > ----- Original Message ----- >> > >> >> From: "Pavol Pitonak" >> > >> >> To: "Pete Muir" >> > >> >> Cc: devtools at redhat.com, "Rick Wagner" >> > >> >> Sent: Thursday, July 7, 2016 4:50:19 AM >> > >> >> Subject: Re: [Devtools] Fix an installer problem with a >> server-side >> > >> >> change? >> > >> >> >> > >> >> It's not installing CDK 2.0.0-beta3 but the one specified in [1]. >> The >> > >> >> mentioned URL is only used for finding out whether the user >> provided >> > >> >> correct >> > >> >> username/password and whether he had agreed with T&C. >> > >> >> >> > >> >> [1] >> > >> >> >> https://github.com/redhat-developer-tooling/developer-platform-install/blob/master/requirements.json#L7 >> > >> >> >> > >> >> On Thu, Jul 7, 2016 at 1:40 PM, Pete Muir < pmuir at redhat.com > >> wrote: >> > >> >> >> > >> >> >> > >> >> On 6 July 2016 at 20:02, Rick Wagner < rwagner at redhat.com > >> wrote: >> > >> >> > Hello DevTools, >> > >> >> > >> > >> >> > It seems we have a problem with the current version of the >> > >> >> > Development >> > >> >> > Suite >> > >> >> > installer. We have at least 2 new customer cases reporting >> inability >> > >> >> > to >> > >> >> > install due to the message dialogue "Terms and Conditions for >> the CDK >> > >> >> > have >> > >> >> > not been signed". >> > >> >> > >> > >> >> > This is concerning because we're also seeing similar activity on >> > >> >> > non-support >> > >> >> > channels. It's also worth noting that not every user that has a >> > >> >> > problem >> > >> >> > reports it-- some just give up and move on. There is enough >> volume >> > >> >> > here >> > >> >> > that we probably should treat this with some urgency. >> > >> >> > >> > >> >> > It seems likely the relevant code (thanks for highlighting this, >> > >> >> > Alexey) >> > >> >> > is >> > >> >> > below: >> > >> >> > >> > >> >> > ------------------------------------------------- >> > >> >> > >> > >> >> > login() { >> > >> >> > this.authFailed = false; >> > >> >> > this.tandcNotSigned = false; >> > >> >> > >> > >> >> > let req = { >> > >> >> > method: 'GET', >> > >> >> > url: >> > >> >> > ' >> > >> >> > >> https://developers.redhat.com/download-manager/rest/tc-accepted?downloadURL=/file/cdk-2.0.0-beta3.zip >> > >> >> > ', >> > >> >> > <<<<<<<<<---- returns 'false' when not approved >> > >> >> >> > >> >> I noticed when reading this that this code appears to be >> downloading >> > >> >> CDK 2.0.0-beta3 which implies that either this is an old version >> of >> > >> >> the installer, or the installer is installing a very old CDK... >> > >> >> >> > >> >> > headers: { >> > >> >> > 'Authorization': 'Basic ' + this.base64.encode(this.username + >> ':' + >> > >> >> > this.password) >> > >> >> > } >> > >> >> > }; >> > >> >> > >> > >> >> > this.http(req) >> > >> >> > .then(this.handleHttpSuccess.bind(this)) >> > >> >> > .catch(this.handleHttpFailure.bind(this)); >> > >> >> > } >> > >> >> > >> > >> >> > --------------------------------- >> > >> >> > >> > >> >> > >> > >> >> > So we have users getting denied use of our product. Do we >> require a >> > >> >> > rebuild >> > >> >> > immediately? Maybe. >> > >> >> > >> > >> >> > How about if we changed the rest service >> > >> >> > ( >> https://developers.redhat.com/download-manager/rest/tc-accepted ) >> > >> >> > so >> > >> >> > it >> > >> >> > includes a peak at an override database as well as whatever it's >> > >> >> > currently >> > >> >> > doing now? >> > >> >> > >> > >> >> > In that way, we could have the users pop over to a 'yes, I >> agree to >> > >> >> > the >> > >> >> > terms' page to insert an entry into the database. The rest >> service >> > >> >> > could >> > >> >> > use something like the provided username as a key to ensure a >> 'true' >> > >> >> > is >> > >> >> > returned. >> > >> >> > >> > >> >> > >> > >> >> > Or not. Is there a better way to fix this? >> > >> >> > >> > >> >> > Please consider, we need to fix this sooner rather than >> later.... >> > >> >> > >> > >> >> > Thanks, >> > >> >> > >> > >> >> > Rick >> > >> >> > >> > >> >> > >> > >> >> > _______________________________________________ >> > >> >> > 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 rstryker at redhat.com Tue Jul 12 18:10:38 2016 From: rstryker at redhat.com (Robert Stryker) Date: Tue, 12 Jul 2016 14:10:38 -0400 Subject: [Devtools] What *is* the 'default Unix socket location' for Docker? In-Reply-To: References: <20160712092745.GC56230@nineveh.local> Message-ID: > I didn't use the 'Servers' view to start the CDK and went off to manipulate it from the command line Mind listing those steps in a jira? Ideally, we should be able to handle user error gracefully without botching up the works, so steps to replicate may help me understand how the uninformed user may make a mess of things ;) On Tue, Jul 12, 2016 at 11:31 AM, Rick Wagner wrote: > Hello All, > > Many thanks for these great tips, the Development Suite has performed > flawlessly. (The fault was mine. I didn't use the 'Servers' view to start > the CDK and went off to manipulate it from the command line. When I used > the Developer Studio provided tools, everything just worked.) > > Thanks, > > Rick > > > On Tue, Jul 12, 2016 at 4:27 AM, Hardy Ferentschik > wrote: > >> Hi, >> >> On Tue, 12-Jul-2016 11:25, Praveen Kumar wrote: >> > On Tue, Jul 12, 2016 at 11:08 AM, Pete Muir wrote: >> > > tcp://10.1.2.2:2375 >> > >> > Pete, I think development suite get those details (docker env to >> > connect external tooling) from vagrant service manager. >> >> +1 Also my understanding. There should really nothing be to be configured. >> It might be that the CDK did not boot/start correctly or something else >> went >> wrong. Would be interesting to know whether the CDK is up and running and >> whether 'vagrant service-manager env' returns the DOCKER settings. >> >> --Hardy >> >> > > _______________________________________________ > Devtools mailing list > Devtools at redhat.com > https://www.redhat.com/mailman/listinfo/devtools > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From dusty at dustymabe.com Tue Jul 12 20:57:29 2016 From: dusty at dustymabe.com (Dusty Mabe) Date: Tue, 12 Jul 2016 16:57:29 -0400 Subject: [Devtools] setup cdk in JBDS Message-ID: <99b9a1db-9971-ebd8-587a-a8ff955d1b14@dustymabe.com> https://access.redhat.com/articles/2255401#set-up-the-container-development-kit-in-jboss-developer-studio >From the above article it tells me - Press the Ctrl and 3 keys and in the Quick Access bar, type Launch CDK. - From the results, click Launch CDK Server. I can't find Launch CDK anywhere. What am I doing wrong? I used the all in one installer on windows. I have version: 10.0.0.GA-v20160615-1853-B33 installed Dusty From alkazako at redhat.com Tue Jul 12 21:11:07 2016 From: alkazako at redhat.com (Alexey Kazakov) Date: Tue, 12 Jul 2016 17:11:07 -0400 Subject: [Devtools] setup cdk in JBDS In-Reply-To: <99b9a1db-9971-ebd8-587a-a8ff955d1b14@dustymabe.com> References: <99b9a1db-9971-ebd8-587a-a8ff955d1b14@dustymabe.com> Message-ID: <57855CEB.10207@redhat.com> I think it's a side effect of renaming "CDK Server Adapter" to "Container Development Environment". It's impossible to add keywords for artefacts in Eclipse for Quick Access bar. So we have to keep CDK in the adapter type/name to be able to access our CDK Server adapter via Quick Access. Rob, could you please create a JIRA for that issue and investigate when we have to keep "CDK" then we can discuss if we should change the adapter type. On 07/12/2016 04:57 PM, Dusty Mabe wrote: > https://access.redhat.com/articles/2255401#set-up-the-container-development-kit-in-jboss-developer-studio > > >From the above article it tells me > - Press the Ctrl and 3 keys and in the Quick Access bar, type Launch CDK. > - From the results, click Launch CDK Server. > > I can't find Launch CDK anywhere. What am I doing wrong? I used the all in one installer on windows. > > I have version: 10.0.0.GA-v20160615-1853-B33 installed > > Dusty > > _______________________________________________ > Devtools mailing list > Devtools at redhat.com > https://www.redhat.com/mailman/listinfo/devtools From alkazako at redhat.com Tue Jul 12 21:15:40 2016 From: alkazako at redhat.com (Alexey Kazakov) Date: Tue, 12 Jul 2016 17:15:40 -0400 Subject: [Devtools] setup cdk in JBDS In-Reply-To: <57855CEB.10207@redhat.com> References: <99b9a1db-9971-ebd8-587a-a8ff955d1b14@dustymabe.com> <57855CEB.10207@redhat.com> Message-ID: <57855DFC.5030809@redhat.com> Forgot to mention that since that renaming you need to type "launch container..." or "container deve..." to see "Launch Container Development Environment" in the Quick Access bar. On 07/12/2016 05:11 PM, Alexey Kazakov wrote: > I think it's a side effect of renaming "CDK Server Adapter" to > "Container Development Environment". > It's impossible to add keywords for artefacts in Eclipse for Quick > Access bar. So we have to keep CDK in the adapter type/name to be able > to access our CDK Server adapter via Quick Access. > Rob, could you please create a JIRA for that issue and investigate > when we have to keep "CDK" then we can discuss if we should change the > adapter type. > > > On 07/12/2016 04:57 PM, Dusty Mabe wrote: >> https://access.redhat.com/articles/2255401#set-up-the-container-development-kit-in-jboss-developer-studio >> >> >> >From the above article it tells me >> - Press the Ctrl and 3 keys and in the Quick Access bar, type Launch >> CDK. >> - From the results, click Launch CDK Server. >> >> I can't find Launch CDK anywhere. What am I doing wrong? I used the >> all in one installer on windows. >> >> I have version: 10.0.0.GA-v20160615-1853-B33 installed >> >> Dusty >> >> _______________________________________________ >> 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 From dusty at dustymabe.com Tue Jul 12 21:21:32 2016 From: dusty at dustymabe.com (Dusty Mabe) Date: Tue, 12 Jul 2016 17:21:32 -0400 Subject: [Devtools] setup cdk in JBDS In-Reply-To: <57855DFC.5030809@redhat.com> References: <99b9a1db-9971-ebd8-587a-a8ff955d1b14@dustymabe.com> <57855CEB.10207@redhat.com> <57855DFC.5030809@redhat.com> Message-ID: <4bdfe3cf-24ba-948d-15c2-dfe257d2f460@dustymabe.com> On 07/12/2016 05:15 PM, Alexey Kazakov wrote: > Forgot to mention that since that renaming you need to type "launch > container..." or "container deve..." to see "Launch Container > Development Environment" in the Quick Access bar. Thanks, That helped me find it. Still no success getting it up though. Now I see this when the box is being brought up by vagrant. ``` ==> default: Waiting for machine to boot. This may take a few minutes... The guest machine entered an invalid state while waiting for it to boot. Valid states are 'starting, running'. The machine is in the 'poweroff' state. Please verify everything is configured properly and try again. If the provider you're using has a GUI that comes with it, it is often helpful to open that and watch the machine, since the GUI often has more helpful error messages than Vagrant can retrieve. For example, if you're using VirtualBox, run `vagrant up` while the VirtualBox GUI is open. The primary issue for this error is that the provider you're using is not properly configured. This is very rarely a Vagrant issue. ``` I also can't bring up the virtualbox GUI at all. It just won't start. I don't really know how to debug on Windows so.... Dusty From jmaury at redhat.com Tue Jul 12 21:27:34 2016 From: jmaury at redhat.com (Jean-Francois Maury) Date: Tue, 12 Jul 2016 23:27:34 +0200 Subject: [Devtools] setup cdk in JBDS In-Reply-To: <4bdfe3cf-24ba-948d-15c2-dfe257d2f460@dustymabe.com> References: <99b9a1db-9971-ebd8-587a-a8ff955d1b14@dustymabe.com> <57855CEB.10207@redhat.com> <57855DFC.5030809@redhat.com> <4bdfe3cf-24ba-948d-15c2-dfe257d2f460@dustymabe.com> Message-ID: Then if you can't bring the VirtualBox GUI, then you should check your VirtualBox installation. What is the error you got when you launch the VirtualBox GUI ? Jeff On Tue, Jul 12, 2016 at 11:21 PM, Dusty Mabe wrote: > > On 07/12/2016 05:15 PM, Alexey Kazakov wrote: > > Forgot to mention that since that renaming you need to type "launch > > container..." or "container deve..." to see "Launch Container > > Development Environment" in the Quick Access bar. > > Thanks, > > That helped me find it. > > Still no success getting it up though. Now I see this when the box is > being brought up by vagrant. > > ``` > ==> default: Waiting for machine to boot. This may take a few minutes... > The guest machine entered an invalid state while waiting for it > to boot. Valid states are 'starting, running'. The machine is in the > 'poweroff' state. Please verify everything is configured > properly and try again. > > If the provider you're using has a GUI that comes with it, > it is often helpful to open that and watch the machine, since the > GUI often has more helpful error messages than Vagrant can retrieve. > For example, if you're using VirtualBox, run `vagrant up` while the > VirtualBox GUI is open. > > The primary issue for this error is that the provider you're using > is not properly configured. This is very rarely a Vagrant issue. > ``` > > > I also can't bring up the virtualbox GUI at all. It just won't start. > I don't really know how to debug on Windows so.... > > Dusty > > _______________________________________________ > Devtools mailing list > Devtools at redhat.com > https://www.redhat.com/mailman/listinfo/devtools > -------------- next part -------------- An HTML attachment was scrubbed... URL: From dusty at dustymabe.com Tue Jul 12 21:29:50 2016 From: dusty at dustymabe.com (Dusty Mabe) Date: Tue, 12 Jul 2016 17:29:50 -0400 Subject: [Devtools] setup cdk in JBDS In-Reply-To: References: <99b9a1db-9971-ebd8-587a-a8ff955d1b14@dustymabe.com> <57855CEB.10207@redhat.com> <57855DFC.5030809@redhat.com> <4bdfe3cf-24ba-948d-15c2-dfe257d2f460@dustymabe.com> Message-ID: On 07/12/2016 05:27 PM, Jean-Francois Maury wrote: > Then if you can't bring the VirtualBox GUI, then you should check your VirtualBox installation. What is the error you got when you launch the VirtualBox GUI ? There is no error. It just never comes up. It thinks for a second and then nothing happens. Any advice on troubleshooting? Dusty From jmaury at redhat.com Tue Jul 12 21:32:42 2016 From: jmaury at redhat.com (Jean-Francois Maury) Date: Tue, 12 Jul 2016 23:32:42 +0200 Subject: [Devtools] setup cdk in JBDS In-Reply-To: References: <99b9a1db-9971-ebd8-587a-a8ff955d1b14@dustymabe.com> <57855CEB.10207@redhat.com> <57855DFC.5030809@redhat.com> <4bdfe3cf-24ba-948d-15c2-dfe257d2f460@dustymabe.com> Message-ID: What version of Windows are you using ? Bare metal machine or through VNC/RDP/.... ? Jeff On Tue, Jul 12, 2016 at 11:29 PM, Dusty Mabe wrote: > > > On 07/12/2016 05:27 PM, Jean-Francois Maury wrote: > > Then if you can't bring the VirtualBox GUI, then you should check your > VirtualBox installation. What is the error you got when you launch the > VirtualBox GUI ? > > There is no error. It just never comes up. It thinks for a second and > then nothing happens. Any advice on troubleshooting? > > Dusty > -------------- next part -------------- An HTML attachment was scrubbed... URL: From alkazako at redhat.com Tue Jul 12 21:36:24 2016 From: alkazako at redhat.com (Alexey Kazakov) Date: Tue, 12 Jul 2016 17:36:24 -0400 Subject: [Devtools] setup cdk in JBDS In-Reply-To: References: <99b9a1db-9971-ebd8-587a-a8ff955d1b14@dustymabe.com> <57855CEB.10207@redhat.com> <57855DFC.5030809@redhat.com> <4bdfe3cf-24ba-948d-15c2-dfe257d2f460@dustymabe.com> Message-ID: <578562D8.60708@redhat.com> I assume you enabled visualization in BIOS? On 07/12/2016 05:32 PM, Jean-Francois Maury wrote: > What version of Windows are you using ? Bare metal machine or through > VNC/RDP/.... ? > > Jeff > > On Tue, Jul 12, 2016 at 11:29 PM, Dusty Mabe > wrote: > > > > On 07/12/2016 05:27 PM, Jean-Francois Maury wrote: > > Then if you can't bring the VirtualBox GUI, then you should > check your VirtualBox installation. What is the error you got when > you launch the VirtualBox GUI ? > > There is no error. It just never comes up. It thinks for a second and > then nothing happens. Any advice on troubleshooting? > > Dusty > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From alkazako at redhat.com Tue Jul 12 21:37:55 2016 From: alkazako at redhat.com (Alexey Kazakov) Date: Tue, 12 Jul 2016 17:37:55 -0400 Subject: [Devtools] setup cdk in JBDS In-Reply-To: <578562D8.60708@redhat.com> References: <99b9a1db-9971-ebd8-587a-a8ff955d1b14@dustymabe.com> <57855CEB.10207@redhat.com> <57855DFC.5030809@redhat.com> <4bdfe3cf-24ba-948d-15c2-dfe257d2f460@dustymabe.com> <578562D8.60708@redhat.com> Message-ID: <57856333.8020904@redhat.com> virtualization* On 07/12/2016 05:36 PM, Alexey Kazakov wrote: > I assume you enabled visualization in BIOS? > > On 07/12/2016 05:32 PM, Jean-Francois Maury wrote: >> What version of Windows are you using ? Bare metal machine or through >> VNC/RDP/.... ? >> >> Jeff >> >> On Tue, Jul 12, 2016 at 11:29 PM, Dusty Mabe > > wrote: >> >> >> >> On 07/12/2016 05:27 PM, Jean-Francois Maury wrote: >> > Then if you can't bring the VirtualBox GUI, then you should >> check your VirtualBox installation. What is the error you got >> when you launch the VirtualBox GUI ? >> >> There is no error. It just never comes up. It thinks for a second and >> then nothing happens. Any advice on troubleshooting? >> >> Dusty >> >> > -------------- next part -------------- An HTML attachment was scrubbed... URL: From tmancini at redhat.com Tue Jul 12 21:55:06 2016 From: tmancini at redhat.com (Todd Mancini) Date: Tue, 12 Jul 2016 14:55:06 -0700 Subject: [Devtools] setup cdk in JBDS Message-ID: <5602657569852275991@unknownmsgid> And, even more basic: did you reboot and try again? (hey, it's Windows...) Hyper -V is NOT installed, correct? Sent from my phone, so anticipate hilarious autocorrects ------------------------------ From: Alexey Kazakov Sent: ?7/?12/?2016 5:38 PM To: Jean-Francois Maury ; Dusty Mabe Cc: devtools at redhat.com Subject: Re: [Devtools] setup cdk in JBDS virtualization* On 07/12/2016 05:36 PM, Alexey Kazakov wrote: I assume you enabled visualization in BIOS? On 07/12/2016 05:32 PM, Jean-Francois Maury wrote: What version of Windows are you using ? Bare metal machine or through VNC/RDP/.... ? Jeff On Tue, Jul 12, 2016 at 11:29 PM, Dusty Mabe wrote: > > > On 07/12/2016 05:27 PM, Jean-Francois Maury wrote: > > Then if you can't bring the VirtualBox GUI, then you should check your > VirtualBox installation. What is the error you got when you launch the > VirtualBox GUI ? > > There is no error. It just never comes up. It thinks for a second and > then nothing happens. Any advice on troubleshooting? > > Dusty > -------------- 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 dusty at dustymabe.com Tue Jul 12 22:04:02 2016 From: dusty at dustymabe.com (Dusty Mabe) Date: Tue, 12 Jul 2016 18:04:02 -0400 Subject: [Devtools] setup cdk in JBDS In-Reply-To: <5602657569852275991@unknownmsgid> References: <5602657569852275991@unknownmsgid> Message-ID: I think hyper-v is installed.. Maybe that is the issue. Dusty On 07/12/2016 05:55 PM, Todd Mancini wrote: > And, even more basic: did you reboot and try again? (hey, it's Windows...) > > Hyper -V is NOT installed, correct? > > Sent from my phone, so anticipate hilarious autocorrects > ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ > From: Alexey Kazakov > Sent: ?7/?12/?2016 5:38 PM > To: Jean-Francois Maury ; Dusty Mabe > Cc: devtools at redhat.com > Subject: Re: [Devtools] setup cdk in JBDS > > virtualization* > > On 07/12/2016 05:36 PM, Alexey Kazakov wrote: >> I assume you enabled visualization in BIOS? >> >> On 07/12/2016 05:32 PM, Jean-Francois Maury wrote: >>> What version of Windows are you using ? Bare metal machine or through VNC/RDP/.... ? >>> >>> Jeff >>> >>> On Tue, Jul 12, 2016 at 11:29 PM, Dusty Mabe > wrote: >>> >>> >>> >>> On 07/12/2016 05:27 PM, Jean-Francois Maury wrote: >>> > Then if you can't bring the VirtualBox GUI, then you should check your VirtualBox installation. What is the error you got when you launch the VirtualBox GUI ? >>> >>> There is no error. It just never comes up. It thinks for a second and >>> then nothing happens. Any advice on troubleshooting? >>> >>> Dusty >>> >>> >> > > > > _______________________________________________ > 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 Tue Jul 12 22:06:19 2016 From: jmaury at redhat.com (Jean-Francois Maury) Date: Wed, 13 Jul 2016 00:06:19 +0200 Subject: [Devtools] setup cdk in JBDS In-Reply-To: References: <5602657569852275991@unknownmsgid> Message-ID: Hyper-V is not compatible with VirtualBox Jeff On Wed, Jul 13, 2016 at 12:04 AM, Dusty Mabe wrote: > I think hyper-v is installed.. Maybe that is the issue. > > Dusty > On 07/12/2016 05:55 PM, Todd Mancini wrote: > > And, even more basic: did you reboot and try again? (hey, it's Windows...) > > Hyper -V is NOT installed, correct? > > Sent from my phone, so anticipate hilarious autocorrects > ------------------------------ > From: Alexey Kazakov > Sent: ?7/?12/?2016 5:38 PM > To: Jean-Francois Maury ; Dusty Mabe > > Cc: devtools at redhat.com > Subject: Re: [Devtools] setup cdk in JBDS > > virtualization* > > On 07/12/2016 05:36 PM, Alexey Kazakov wrote: > > I assume you enabled visualization in BIOS? > > On 07/12/2016 05:32 PM, Jean-Francois Maury wrote: > > What version of Windows are you using ? Bare metal machine or through > VNC/RDP/.... ? > > Jeff > > On Tue, Jul 12, 2016 at 11:29 PM, Dusty Mabe wrote: > >> >> >> On 07/12/2016 05:27 PM, Jean-Francois Maury wrote: >> > Then if you can't bring the VirtualBox GUI, then you should check your >> VirtualBox installation. What is the error you got when you launch the >> VirtualBox GUI ? >> >> There is no error. It just never comes up. It thinks for a second and >> then nothing happens. Any advice on troubleshooting? >> >> Dusty >> > > > > > > _______________________________________________ > Devtools mailing listDevtools at redhat.comhttps://www.redhat.com/mailman/listinfo/devtools > > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From dusty at dustymabe.com Wed Jul 13 02:25:20 2016 From: dusty at dustymabe.com (Dusty Mabe) Date: Tue, 12 Jul 2016 22:25:20 -0400 Subject: [Devtools] setup cdk in JBDS In-Reply-To: References: <5602657569852275991@unknownmsgid> Message-ID: On 07/12/2016 06:06 PM, Jean-Francois Maury wrote: > Hyper-V is not compatible with VirtualBox > Indeed. That is the issue. Would have been great if my computer would have done something other than reboot when this issue came up. If the installer is going to install vbox should we have the installer detect if hyper-v is enabled and warn ? Dusty From mmalina at redhat.com Wed Jul 13 08:04:45 2016 From: mmalina at redhat.com (Martin Malina) Date: Wed, 13 Jul 2016 10:04:45 +0200 Subject: [Devtools] setup cdk in JBDS In-Reply-To: References: <5602657569852275991@unknownmsgid> Message-ID: > On 13. 7. 2016, at 4:25, Dusty Mabe wrote: > > > > On 07/12/2016 06:06 PM, Jean-Francois Maury wrote: >> Hyper-V is not compatible with VirtualBox >> > > Indeed. That is the issue. Would have been great if my computer would > have done something other than reboot when this issue came up. > > If the installer is going to install vbox should we have the installer > detect if hyper-v is enabled and warn ? I'm really surprised that VirtualBox GUI wouldn't come up at all. I would expect it to show up, but starting a VM would fail with "VT-x/AMD-V hardware acceleration is not available on your system" or similar. I actually think this is what happened when I tried hyper-v a month or so ago. Can somebody confirm / deny that VirtualBox GUI won't start at all when hyper-v is enabled? That seems really strange. -Martin > > Dusty > > _______________________________________________ > Devtools mailing list > Devtools at redhat.com > https://www.redhat.com/mailman/listinfo/devtools From jmaury at redhat.com Wed Jul 13 08:25:04 2016 From: jmaury at redhat.com (Jean-Francois Maury) Date: Wed, 13 Jul 2016 10:25:04 +0200 Subject: [Devtools] setup cdk in JBDS In-Reply-To: References: <5602657569852275991@unknownmsgid> Message-ID: I had the same behavior when hyperv was enabled Jeff Le 13 juil. 2016 10:16, "Martin Malina" a ?crit : > > > On 13. 7. 2016, at 4:25, Dusty Mabe wrote: > > > > > > > > On 07/12/2016 06:06 PM, Jean-Francois Maury wrote: > >> Hyper-V is not compatible with VirtualBox > >> > > > > Indeed. That is the issue. Would have been great if my computer would > > have done something other than reboot when this issue came up. > > > > If the installer is going to install vbox should we have the installer > > detect if hyper-v is enabled and warn ? > > I'm really surprised that VirtualBox GUI wouldn't come up at all. I would > expect it to show up, but starting a VM would fail with "VT-x/AMD-V > hardware acceleration is not available on your system" or similar. I > actually think this is what happened when I tried hyper-v a month or so ago. > Can somebody confirm / deny that VirtualBox GUI won't start at all when > hyper-v is enabled? That seems really strange. > > -Martin > > > > > Dusty > > > > _______________________________________________ > > Devtools mailing list > > Devtools at redhat.com > > https://www.redhat.com/mailman/listinfo/devtools > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From dusty at dustymabe.com Wed Jul 13 12:21:45 2016 From: dusty at dustymabe.com (Dusty Mabe) Date: Wed, 13 Jul 2016 08:21:45 -0400 Subject: [Devtools] setup cdk in JBDS In-Reply-To: References: <5602657569852275991@unknownmsgid> Message-ID: <39fca8e1-bc28-31df-0d48-6634a55e8c7f@dustymabe.com> On 07/13/2016 04:04 AM, Martin Malina wrote: > >> On 13. 7. 2016, at 4:25, Dusty Mabe wrote: >> >> >> >> On 07/12/2016 06:06 PM, Jean-Francois Maury wrote: >>> Hyper-V is not compatible with VirtualBox >>> >> >> Indeed. That is the issue. Would have been great if my computer would >> have done something other than reboot when this issue came up. >> >> If the installer is going to install vbox should we have the installer >> detect if hyper-v is enabled and warn ? > > I'm really surprised that VirtualBox GUI wouldn't come up at all. I would expect it to show up, but starting a VM would fail with "VT-x/AMD-V hardware acceleration is not available on your system" or similar. I actually think this is what happened when I tried hyper-v a month or so ago. > Can somebody confirm / deny that VirtualBox GUI won't start at all when hyper-v is enabled? That seems really strange. So initially I just thought it was Virtualbox. So I uninstalled virtualbox and I installed vbox 5.0 from oracle's site. After installing vbox outside of the JBDS installer I was able to bring up the GUI but when I tried to start a VM the system would crash and reboot. So with the vbox from the JBDS installer the GUI wouldn't even start. With vbox 5.0 from oracle site, the system would crash. I don't know if this is the exact behavior on everyones system. Just reporting what I think I observed. Dusty From rwagner at redhat.com Wed Jul 13 15:47:51 2016 From: rwagner at redhat.com (Rick Wagner) Date: Wed, 13 Jul 2016 10:47:51 -0500 Subject: [Devtools] What *is* the 'default Unix socket location' for Docker? In-Reply-To: References: <20160712092745.GC56230@nineveh.local> Message-ID: Hi Rob and All, Closing the loop on this one. Per Rob's request, I've documented the issue at [1]. Thanks! Rick [1] https://issues.jboss.org/browse/JBIDE-22734 On Tue, Jul 12, 2016 at 1:10 PM, Robert Stryker wrote: > > I didn't use the 'Servers' view to start the CDK and went off to > manipulate it from the command line > > Mind listing those steps in a jira? Ideally, we should be able to handle > user error gracefully without botching up the works, so steps to replicate > may help me understand how the uninformed user may make a mess of things ;) > > On Tue, Jul 12, 2016 at 11:31 AM, Rick Wagner wrote: > >> Hello All, >> >> Many thanks for these great tips, the Development Suite has performed >> flawlessly. (The fault was mine. I didn't use the 'Servers' view to start >> the CDK and went off to manipulate it from the command line. When I used >> the Developer Studio provided tools, everything just worked.) >> >> Thanks, >> >> Rick >> >> >> On Tue, Jul 12, 2016 at 4:27 AM, Hardy Ferentschik >> wrote: >> >>> Hi, >>> >>> On Tue, 12-Jul-2016 11:25, Praveen Kumar wrote: >>> > On Tue, Jul 12, 2016 at 11:08 AM, Pete Muir wrote: >>> > > tcp://10.1.2.2:2375 >>> > >>> > Pete, I think development suite get those details (docker env to >>> > connect external tooling) from vagrant service manager. >>> >>> +1 Also my understanding. There should really nothing be to be >>> configured. >>> It might be that the CDK did not boot/start correctly or something else >>> went >>> wrong. Would be interesting to know whether the CDK is up and running and >>> whether 'vagrant service-manager env' returns the DOCKER settings. >>> >>> --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 Wed Jul 13 18:12:01 2016 From: bsutter at redhat.com (Burr Sutter) Date: Wed, 13 Jul 2016 14:12:01 -0400 Subject: [Devtools] Questions on containers... In-Reply-To: <20160629082225.GC10832@nineveh.lan> References: <20160629082225.GC10832@nineveh.lan> Message-ID: On Wed, Jun 29, 2016 at 4:22 AM, Hardy Ferentschik wrote: > Hi, > > On Fri, 24-Jun-2016 14:06, Burr Sutter wrote: > > We are attempting to get a public forum started. I can generate a lot > of > > newbie questions, but we need some folks to answer :-) > > > > https://developer.jboss.org/thread/271221 > > OOI, why developer.jboss.org? This is the worst choice possible imo. > There is a whole range of things wrong with developer.jboss.org( eg speed > and the actual editing experience). > We already had the infrastructure for hosting forums at jboss.org developers.redhat.com is basically a "static site", so you we took a short-cut and leverage existing infrastructure. > > But that apart, how do you see anyone signed up for developers.redhat.com > contribute to this forum? So I am currently logged in to > developers.redhat.com > and follow this link - https://developer.jboss.org/en/products/cdk/ - from > http://developers.redhat.com/forums/. > > Looking at the banners I have the impressions I am still in the > developers.redhat.com > context. But hey, I am logged out. Trying to now log in again, get me to > this error > page: > > >>> > Duplicate account > > You are trying to log in via duplicate account. Please use your master > account. > Master account is hardy.ferentschik. > >>> > > So it seems that there are conflicts between my JBoss account and the > Developers > Red Hat one. But even then, say I did not have a JBoss account, would I > now have to > register to one in order to participate in the blog? And how does one > know. The > whole L&F is kept in a way to suggest you are still on Red Hat Developers. > > It keeps amazing me how many logins, re-directs, license agreements, etc > one has to > jump using developers.redhat.com. This is patch work at best. > We do have a lot of usability work to do. > > If I'd tried the site having no ties to Red Hat, you'd already lost me. > :-) Do you have a concrete proposal on how to "fix it"? Assume nothing...we made a big push on "features" for Summit/DevNation...now we have lots of "clean up" to sort out. > > --Hardy > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From degolovi at redhat.com Wed Jul 13 18:37:14 2016 From: degolovi at redhat.com (Denis Golovin) Date: Wed, 13 Jul 2016 14:37:14 -0400 (EDT) Subject: [Devtools] Fix an installer problem with a server-side change? In-Reply-To: References: <286619954.4301173.1467934040488.JavaMail.zimbra@redhat.com> <1389444465.4733098.1468050201343.JavaMail.zimbra@redhat.com> <1208091986.5139288.1468305066328.JavaMail.zimbra@redhat.com> Message-ID: <2002283504.5473463.1468435034722.JavaMail.zimbra@redhat.com> Thanks Rob! I looked through code you pointed out and it uses the same approach we use right now in DevSuite, we check for T&C's by accessing specific file trough download manager URL. If someone deletes this specific file our check is broken, that is why we want something based on product id or stable URL, rather that file. Thanks, Denis ----- Original Message ----- > From: "Robert Stryker" > To: "Pete Muir" > Cc: "Denis Golovin" , devtools at redhat.com, "Rick Wagner" > Sent: Tuesday, July 12, 2016 11:02:01 AM > Subject: Re: [Devtools] Fix an installer problem with a server-side change? > > If you find it hard to reach him, you can also check some of the code in > jbosstools-base, specifically in 'runtimes' folder. We have some code > there that checks whether we have permissions for a given file, which > basically means is the t&c accepted. > > Check in DownloadManagerWorkflowUtility for some parts. getWorkflowStatus > is one method that may provide code for you to copy. > > But there may be newer or cleaner code from David Hladky... > > - Rob Stryker > > On Tue, Jul 12, 2016 at 3:23 AM, Pete Muir wrote: > > > David H and mark N are the right people. > > On 12 Jul 2016 7:31 a.m., "Denis Golovin" wrote: > > > >> Pete, > >> > >> it seems T&C's workflow is really simple now, T&C's just signed > >> when registrations is done. It seems that this request could be > >> just https://developers.redhat.com/download-manager/rest/tc-accepted > >> without any additional parameters. > >> > >> Who should I discuss it with? Is David Hladky right person? > >> > >> Thanks, > >> Denis > >> > >> ----- Original Message ----- > >> > From: "Pete Muir" > >> > To: "Denis Golovin" > >> > Cc: "Pavol Pitonak" , devtools at redhat.com, "Rick > >> Wagner" > >> > Sent: Monday, July 11, 2016 4:32:56 AM > >> > Subject: Re: [Devtools] Fix an installer problem with a server-side > >> change? > >> > > >> > Exactly - I'm worried that in a couple of years time, someone will > >> > delete that download, or upgrade the REST interface, not realising > >> > that the installer is (ab)using it for something else... > >> > > >> > On 9 July 2016 at 08:43, Denis Golovin wrote: > >> > > There is no issue opened for this. Do you mean rest service should > >> support > >> > > requests to check T&C's using product-id instead of specific file. > >> > > Something similar to > >> > > > >> https://developers.redhat.com/download-manager/rest/tc-accepted?productId=cdk > >> > > > >> > > ----- Original Message ----- > >> > >> From: "Pete Muir" > >> > >> To: "Denis Golovin" > >> > >> Cc: "Pavol Pitonak" , devtools at redhat.com, > >> "Rick > >> > >> Wagner" > >> > >> Sent: Friday, July 8, 2016 7:52:30 AM > >> > >> Subject: Re: [Devtools] Fix an installer problem with a server-side > >> > >> change? > >> > >> > >> > >> Do we have an issue to replace this with a proper T&C check that > >> > >> doesn't involve the name of a file that might get changed without > >> > >> someone understanding the installer depends on it? > >> > >> > >> > >> On 8 July 2016 at 00:27, Denis Golovin wrote: > >> > >> > That is correct answer. This url is only to verify T&C's are > >> signed. > >> > >> > > >> > >> > ----- Original Message ----- > >> > >> >> From: "Pavol Pitonak" > >> > >> >> To: "Pete Muir" > >> > >> >> Cc: devtools at redhat.com, "Rick Wagner" > >> > >> >> Sent: Thursday, July 7, 2016 4:50:19 AM > >> > >> >> Subject: Re: [Devtools] Fix an installer problem with a > >> server-side > >> > >> >> change? > >> > >> >> > >> > >> >> It's not installing CDK 2.0.0-beta3 but the one specified in [1]. > >> The > >> > >> >> mentioned URL is only used for finding out whether the user > >> provided > >> > >> >> correct > >> > >> >> username/password and whether he had agreed with T&C. > >> > >> >> > >> > >> >> [1] > >> > >> >> > >> https://github.com/redhat-developer-tooling/developer-platform-install/blob/master/requirements.json#L7 > >> > >> >> > >> > >> >> On Thu, Jul 7, 2016 at 1:40 PM, Pete Muir < pmuir at redhat.com > > >> wrote: > >> > >> >> > >> > >> >> > >> > >> >> On 6 July 2016 at 20:02, Rick Wagner < rwagner at redhat.com > > >> wrote: > >> > >> >> > Hello DevTools, > >> > >> >> > > >> > >> >> > It seems we have a problem with the current version of the > >> > >> >> > Development > >> > >> >> > Suite > >> > >> >> > installer. We have at least 2 new customer cases reporting > >> inability > >> > >> >> > to > >> > >> >> > install due to the message dialogue "Terms and Conditions for > >> the CDK > >> > >> >> > have > >> > >> >> > not been signed". > >> > >> >> > > >> > >> >> > This is concerning because we're also seeing similar activity on > >> > >> >> > non-support > >> > >> >> > channels. It's also worth noting that not every user that has a > >> > >> >> > problem > >> > >> >> > reports it-- some just give up and move on. There is enough > >> volume > >> > >> >> > here > >> > >> >> > that we probably should treat this with some urgency. > >> > >> >> > > >> > >> >> > It seems likely the relevant code (thanks for highlighting this, > >> > >> >> > Alexey) > >> > >> >> > is > >> > >> >> > below: > >> > >> >> > > >> > >> >> > ------------------------------------------------- > >> > >> >> > > >> > >> >> > login() { > >> > >> >> > this.authFailed = false; > >> > >> >> > this.tandcNotSigned = false; > >> > >> >> > > >> > >> >> > let req = { > >> > >> >> > method: 'GET', > >> > >> >> > url: > >> > >> >> > ' > >> > >> >> > > >> https://developers.redhat.com/download-manager/rest/tc-accepted?downloadURL=/file/cdk-2.0.0-beta3.zip > >> > >> >> > ', > >> > >> >> > <<<<<<<<<---- returns 'false' when not approved > >> > >> >> > >> > >> >> I noticed when reading this that this code appears to be > >> downloading > >> > >> >> CDK 2.0.0-beta3 which implies that either this is an old version > >> of > >> > >> >> the installer, or the installer is installing a very old CDK... > >> > >> >> > >> > >> >> > headers: { > >> > >> >> > 'Authorization': 'Basic ' + this.base64.encode(this.username + > >> ':' + > >> > >> >> > this.password) > >> > >> >> > } > >> > >> >> > }; > >> > >> >> > > >> > >> >> > this.http(req) > >> > >> >> > .then(this.handleHttpSuccess.bind(this)) > >> > >> >> > .catch(this.handleHttpFailure.bind(this)); > >> > >> >> > } > >> > >> >> > > >> > >> >> > --------------------------------- > >> > >> >> > > >> > >> >> > > >> > >> >> > So we have users getting denied use of our product. Do we > >> require a > >> > >> >> > rebuild > >> > >> >> > immediately? Maybe. > >> > >> >> > > >> > >> >> > How about if we changed the rest service > >> > >> >> > ( > >> https://developers.redhat.com/download-manager/rest/tc-accepted ) > >> > >> >> > so > >> > >> >> > it > >> > >> >> > includes a peak at an override database as well as whatever it's > >> > >> >> > currently > >> > >> >> > doing now? > >> > >> >> > > >> > >> >> > In that way, we could have the users pop over to a 'yes, I > >> agree to > >> > >> >> > the > >> > >> >> > terms' page to insert an entry into the database. The rest > >> service > >> > >> >> > could > >> > >> >> > use something like the provided username as a key to ensure a > >> 'true' > >> > >> >> > is > >> > >> >> > returned. > >> > >> >> > > >> > >> >> > > >> > >> >> > Or not. Is there a better way to fix this? > >> > >> >> > > >> > >> >> > Please consider, we need to fix this sooner rather than > >> later.... > >> > >> >> > > >> > >> >> > Thanks, > >> > >> >> > > >> > >> >> > Rick > >> > >> >> > > >> > >> >> > > >> > >> >> > _______________________________________________ > >> > >> >> > 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 > > > > > From dusty at dustymabe.com Wed Jul 13 19:34:23 2016 From: dusty at dustymabe.com (Dusty Mabe) Date: Wed, 13 Jul 2016 15:34:23 -0400 Subject: [Devtools] setup cdk in JBDS In-Reply-To: <57855CEB.10207@redhat.com> References: <99b9a1db-9971-ebd8-587a-a8ff955d1b14@dustymabe.com> <57855CEB.10207@redhat.com> Message-ID: <7fb237d6-c4e0-4141-1d4e-7c0d5b3860fc@dustymabe.com> On 07/12/2016 05:11 PM, Alexey Kazakov wrote: > I think it's a side effect of renaming "CDK Server Adapter" to > "Container Development Environment". > It's impossible to add keywords for artefacts in Eclipse for Quick > Access bar. So we have to keep CDK in the adapter type/name to be able > to access our CDK Server adapter via Quick Access. > Rob, could you please create a JIRA for that issue and investigate when > we have to keep "CDK" then we can discuss if we should change the > adapter type. Rob, Was there a JIRA created for this? Could we link to it here in this thread? From alkazako at redhat.com Wed Jul 13 20:23:27 2016 From: alkazako at redhat.com (Alexey Kazakov) Date: Wed, 13 Jul 2016 16:23:27 -0400 Subject: [Devtools] setup cdk in JBDS In-Reply-To: <7fb237d6-c4e0-4141-1d4e-7c0d5b3860fc@dustymabe.com> References: <99b9a1db-9971-ebd8-587a-a8ff955d1b14@dustymabe.com> <57855CEB.10207@redhat.com> <7fb237d6-c4e0-4141-1d4e-7c0d5b3860fc@dustymabe.com> Message-ID: <5786A33F.90005@redhat.com> I have created it - https://issues.jboss.org/browse/JBIDE-22735 On 07/13/2016 03:34 PM, Dusty Mabe wrote: > > On 07/12/2016 05:11 PM, Alexey Kazakov wrote: >> I think it's a side effect of renaming "CDK Server Adapter" to >> "Container Development Environment". >> It's impossible to add keywords for artefacts in Eclipse for Quick >> Access bar. So we have to keep CDK in the adapter type/name to be able >> to access our CDK Server adapter via Quick Access. >> Rob, could you please create a JIRA for that issue and investigate when >> we have to keep "CDK" then we can discuss if we should change the >> adapter type. > Rob, Was there a JIRA created for this? Could we link to it here in > this thread? > From cdrage at redhat.com Thu Jul 14 14:45:15 2016 From: cdrage at redhat.com (Charlie Drage) Date: Thu, 14 Jul 2016 10:45:15 -0400 Subject: [Devtools] Creating a Kubernetes cluster with Atomic Host just through cloud-init Message-ID: <20160714144515.GA1@7deb827c45c8> One of the benefits of running cloud-init is being able to provision or configure a host on first start-up without having to run everything. It would be *awesome* to be able to have a k8s cluster up-and-running just through cloud-init configuration. Has there been any initiative towards this approach, and if not, perhaps we can contribute upstream towards it? :) (github.com/kubernetes/contrib) I've been a lot lately with Flanel + etcd2 + Kubernetes, so I can help get this up-and-running and create the neccesary config files. -- Charlie Drage Red Hat - Dev Tools / Project Atomic PGP - 4096R/C037D617 http://pgp.mit.edu/pks/lookup?op=get&search=0xDA227403C037D617 From degolovi at redhat.com Wed Jul 20 08:08:22 2016 From: degolovi at redhat.com (Denis Golovin) Date: Wed, 20 Jul 2016 04:08:22 -0400 (EDT) Subject: [Devtools] Development Suite installation question - C/O SME with knowledge of installer edits In-Reply-To: References: <1829398.oJedtQYAuc@x230> <1597469.slTCQpW6SA@x230> <6413734.nWTzG8j3RH@x230> Message-ID: <1960516785.6522026.1469002102802.JavaMail.zimbra@redhat.com> FYI: JIRA created to track this problem: ORG-3470 DevSuite T&C's signing status check doesn't work for users created before May 18th Denis ----- Original Message ----- > From: "Pete Muir" > To: "Rick Wagner" > Cc: devtools at redhat.com, "Mark Newton" > Sent: Thursday, July 7, 2016 11:34:47 AM > Subject: Re: [Devtools] Development Suite installation question - C/O SME with knowledge of installer edits > > On 7 July 2016 at 19:08, Rick Wagner wrote: > > Hello All, > > > > Additional information, this from (no SalesForce acct required) the support > > case at [1]. > > > > The customer is telling us the 'use a new account' workaround was > > successful > > with a Windows 10 machine. A second attempt on a Win 7 machine fails. > > > > The failed effort: > > - Is using the userid 'ryanbuckett' > > - Previously failed effort (the original account) was 'SumaGeethakumari'. > > > > The customer is asking if the downloaded exectuable must be used on the > > machine it was downloaded to? (If the username specified for download and > > installation are the same, is it relevant where the artifact was downloaded > > to?) > > No, the link is usernames. You must use the username you downloaded > with when you run the installer. > > David/Mark, can you check these user accounts - have they signed the > RHEL Developer Suite T&C? > > > > > Thanks, > > > > Rick > > > > [1] https://access.redhat.com/support/cases/01662411 > > > > On Thu, Jul 7, 2016 at 11:40 AM, Pete Muir wrote: > >> > >> Very helpful Robert, as it helps us identify that there is a problem > >> on the server side around older accounts that somehow aren't being > >> properly upgraded. > >> > >> Mark/David, can you treat this as an urgent issue to look in to, as > >> it's getting reported by customers. > >> > >> Rick Wagner is getting more info from customers, but Robert seems to > >> have identified at least one failing path. > >> > >> On 7 July 2016 at 17:29, Robert Kratky wrote: > >> > Follow up: brand new account worked for this user. So: > >> > > >> > - user didn't use social accounts to log in > >> > - orig. account created on dev.rh.com on May 18: doesn't work > >> > - new account created on July 7: works > >> > > >> > Hope this helps a bit. > >> > > >> > Regards, > >> > Robert > >> > > >> > > >> > On 7.?7.?2016 17:33:32, Robert Kratky wrote: > >> > > >> >> Based on a new user comment [1], the "don't use social accounts" > >> >> workaround doesn't seem to work. It might be related to the fact that > >> >> he > >> >> created his RH account on May 18 (i.e. it's not fresh). > >> >> > >> >> I asked the user to try a completely new account, but some less drastic > >> >> solution would be better. > >> >> > >> >> Robert > >> >> > >> >> [1] https://access.redhat.com/articles/2255391#comment-1069221 > >> >> > >> >> > >> >> On 7.?7.?2016 15:58:06, Robert Kratky wrote: > >> >> > >> >> > I updated the text to emphasize that social accounts are not to be > >> >> > used. It now says, basically: > >> >> > > >> >> > 1) log in using RH credentials > >> >> > 2) do not use social accounts > >> >> > 3) if you can't (i.e. you have no RH account), create a new one > >> >> > > >> >> > Robert > >> >> > > >> >> > > >> >> > On 7.?7.?2016 14:42:15, Pete Muir wrote: > >> >> > > >> >> > > Robert, as discussed on the call, you might want to recommend a > >> >> > > "radical" workaround, of just creating a new account entirely, > >> >> > > without > >> >> > > using social media at all. > >> >> > > > >> >> > > On 7 July 2016 at 14:38, Robert Kratky wrote: > >> >> > > > I updated the trouleshooting section in [1] based on the > >> >> > > > discussion during today's program call. Please, have a look and > >> >> > > > let me know > >> >> > > > if what I wrote is accurate -- I cannot test at this moment. > >> >> > > > > >> >> > > > This is what it says now: > >> >> > > > > >> >> > > > ............. > >> >> > > > Terms and Conditions Error > >> >> > > > > >> >> > > > Error: ?Terms and Conditions for CDK have not been signed? > >> >> > > > This error appears on the Log In page when starting the > >> >> > > > Installer. To work around the problem, log in to the Developer > >> >> > > > Portal using > >> >> > > > your Red Hat credentials -- the credentials that you created > >> >> > > > either on > >> >> > > > redhat.com or developers.redhat.com. Do not use your social > >> >> > > > accounts to log > >> >> > > > in. Then start downloading the Installer from Red Hat Development > >> >> > > > Suite > >> >> > > > download page. > >> >> > > > > >> >> > > > If you do not have a Red Hat account, create one at > >> >> > > > developers.redhat.com. > >> >> > > > ............. > >> >> > > > > >> >> > > > Thanks. > >> >> > > > Robert > >> >> > > > > >> >> > > > [1] https://access.redhat.com/articles/2360571#troubleshooting > >> >> > > > > >> >> > > > > >> >> > > > On 7.?7.?2016 10:32:06, Misha Husnain Ali wrote: > >> >> > > > > >> >> > > >> I remember this issue. Is there any way we can identify the > >> >> > > >> paths leading > >> >> > > >> up to this problem and comprehensively test them to provide > >> >> > > >> clear aid to > >> >> > > >> users who may encounter this issue? I'm happy to volunteer to > >> >> > > >> test some of > >> >> > > >> them if we can identify the various paths users may take. > >> >> > > >> > >> >> > > >> > >> >> > > >> -- > >> >> > > >> Misha Husnain Ali > >> >> > > >> Technical Writer 2, CCS Brisbane > >> >> > > >> > >> >> > > >> On Thu, Jul 7, 2016 at 5:38 AM, Denis Golovin > >> >> > > >> wrote: > >> >> > > >> > >> >> > > >> > T&C's signing workflow is not user friendly ATM. > >> >> > > >> > > >> >> > > >> > Workaround mentioned in > >> >> > > >> > https://access.redhat.com/articles/2360571 worked > >> >> > > >> > before for > >> >> > > >> > many dev's who was testing installer. I am going to do check > >> >> > > >> > full T&C's > >> >> > > >> > signing again today > >> >> > > >> > and send update ASAP. > >> >> > > >> > > >> >> > > >> > This problem should be affecting only customers who didn't get > >> >> > > >> > installer > >> >> > > >> > directly from develper.redhat.com > >> >> > > >> > download. > >> >> > > >> > > >> >> > > >> > Denis > >> >> > > >> > > >> >> > > >> > ----- Original Message ----- > >> >> > > >> > > From: "Robert Kratky" > >> >> > > >> > > To: devtools at redhat.com > >> >> > > >> > > Cc: "Rick Wagner" > >> >> > > >> > > Sent: Wednesday, July 6, 2016 8:51:03 AM > >> >> > > >> > > Subject: Re: [Devtools] Development Suite installation > >> >> > > >> > > question - C/O > >> >> > > >> > SME with knowledge of installer edits > >> >> > > >> > > > >> >> > > >> > > On 6.?7.?2016 10:08:09, Rick Wagner wrote: > >> >> > > >> > > > >> >> > > >> > > > Hello DevTools, > >> >> > > >> > > > > >> >> > > >> > > > We have a customer case that deals with the error message > >> >> > > >> > > > "Terms and > >> >> > > >> > > > Conditions for the CDK have not been signed". (Actually, > >> >> > > >> > > > this is the > >> >> > > >> > > > second case in 2 days for this problem.) > >> >> > > >> > > > > >> >> > > >> > > > The customer has tried the suggested workaround, without > >> >> > > >> > > > satisfactory > >> >> > > >> > > > results. ("This error appears on the *Log In* page when > >> >> > > >> > > > starting the > >> >> > > >> > > > Installer. To fix the problem, start downloading the > >> >> > > >> > > > Installer to > >> >> > > >> > ensure > >> >> > > >> > > > the *Terms and Conditions* are viewed and accepted and > >> >> > > >> > > > then cancel the > >> >> > > >> > > > binary download." We offer this suggestion in the > >> >> > > >> > > > knowledge article at > >> >> > > >> > > > [1].) > >> >> > > >> > > > > >> >> > > >> > > > Can a knowledgeable SME please offer ideas about > >> >> > > >> > > > alternative courses of > >> >> > > >> > > > action? > >> >> > > >> > > > >> >> > > >> > > Hi Rick, > >> >> > > >> > > > >> >> > > >> > > The problem happens quite often, apparently. I asked about > >> >> > > >> > > this last > >> >> > > >> > Friday > >> >> > > >> > > in devtools-program [a] -- on behalf of a user who reported > >> >> > > >> > > the problem > >> >> > > >> > in a > >> >> > > >> > > comment under the old version of the Kbase article [b]. > >> >> > > >> > > > >> >> > > >> > > Any workaround would be appreciated. > >> >> > > >> > > > >> >> > > >> > > Thanks. > >> >> > > >> > > > >> >> > > >> > > Robert > >> >> > > >> > > > >> >> > > >> > > [a] > >> >> > > >> > > > >> >> > > >> > > >> >> > > >> > http://post-office.corp.redhat.com/archives/devtools-program/2016-July/msg00001.html > >> >> > > >> > > [b] > >> >> > > >> > > https://access.redhat.com/articles/2255391#comment-1066361 > >> >> > > >> > > > >> >> > > >> > > > Extra credit: Can you please point me to the source code > >> >> > > >> > > > that produces > >> >> > > >> > > > this edit error? A little spelunking by the Support team > >> >> > > >> > > > sometimes > >> >> > > >> > helps > >> >> > > >> > > > with related issues. > >> >> > > >> > > > > >> >> > > >> > > > Thanks! > >> >> > > >> > > > > >> >> > > >> > > > Rick > >> >> > > >> > > > > >> >> > > >> > > > [1] https://access.redhat.com/articles/2360571 > >> > > >> > > >> > _______________________________________________ > >> > 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 > From degolovi at redhat.com Wed Jul 20 08:11:52 2016 From: degolovi at redhat.com (Denis Golovin) Date: Wed, 20 Jul 2016 04:11:52 -0400 (EDT) Subject: [Devtools] Fix an installer problem with a server-side change? In-Reply-To: References: <286619954.4301173.1467934040488.JavaMail.zimbra@redhat.com> <1389444465.4733098.1468050201343.JavaMail.zimbra@redhat.com> <1208091986.5139288.1468305066328.JavaMail.zimbra@redhat.com> Message-ID: <1462824967.6522286.1469002312561.JavaMail.zimbra@redhat.com> FYI: JIRA is created to fix T&C's check in DevSuite to use stable link in download-manager. ORG-3469 Check T&C's signing status without referencing to specific file in download-manager Denis ----- Original Message ----- > From: "Pete Muir" > To: "Denis Golovin" > Cc: ppitonak at redhat.com, "Rick Wagner" , devtools at redhat.com > Sent: Tuesday, July 12, 2016 12:23:39 AM > Subject: Re: [Devtools] Fix an installer problem with a server-side change? > > David H and mark N are the right people. > On 12 Jul 2016 7:31 a.m., "Denis Golovin" wrote: > > > Pete, > > > > it seems T&C's workflow is really simple now, T&C's just signed > > when registrations is done. It seems that this request could be > > just https://developers.redhat.com/download-manager/rest/tc-accepted > > without any additional parameters. > > > > Who should I discuss it with? Is David Hladky right person? > > > > Thanks, > > Denis > > > > ----- Original Message ----- > > > From: "Pete Muir" > > > To: "Denis Golovin" > > > Cc: "Pavol Pitonak" , devtools at redhat.com, "Rick > > Wagner" > > > Sent: Monday, July 11, 2016 4:32:56 AM > > > Subject: Re: [Devtools] Fix an installer problem with a server-side > > change? > > > > > > Exactly - I'm worried that in a couple of years time, someone will > > > delete that download, or upgrade the REST interface, not realising > > > that the installer is (ab)using it for something else... > > > > > > On 9 July 2016 at 08:43, Denis Golovin wrote: > > > > There is no issue opened for this. Do you mean rest service should > > support > > > > requests to check T&C's using product-id instead of specific file. > > > > Something similar to > > > > > > https://developers.redhat.com/download-manager/rest/tc-accepted?productId=cdk > > > > > > > > ----- Original Message ----- > > > >> From: "Pete Muir" > > > >> To: "Denis Golovin" > > > >> Cc: "Pavol Pitonak" , devtools at redhat.com, "Rick > > > >> Wagner" > > > >> Sent: Friday, July 8, 2016 7:52:30 AM > > > >> Subject: Re: [Devtools] Fix an installer problem with a server-side > > > >> change? > > > >> > > > >> Do we have an issue to replace this with a proper T&C check that > > > >> doesn't involve the name of a file that might get changed without > > > >> someone understanding the installer depends on it? > > > >> > > > >> On 8 July 2016 at 00:27, Denis Golovin wrote: > > > >> > That is correct answer. This url is only to verify T&C's are signed. > > > >> > > > > >> > ----- Original Message ----- > > > >> >> From: "Pavol Pitonak" > > > >> >> To: "Pete Muir" > > > >> >> Cc: devtools at redhat.com, "Rick Wagner" > > > >> >> Sent: Thursday, July 7, 2016 4:50:19 AM > > > >> >> Subject: Re: [Devtools] Fix an installer problem with a server-side > > > >> >> change? > > > >> >> > > > >> >> It's not installing CDK 2.0.0-beta3 but the one specified in [1]. > > The > > > >> >> mentioned URL is only used for finding out whether the user > > provided > > > >> >> correct > > > >> >> username/password and whether he had agreed with T&C. > > > >> >> > > > >> >> [1] > > > >> >> > > https://github.com/redhat-developer-tooling/developer-platform-install/blob/master/requirements.json#L7 > > > >> >> > > > >> >> On Thu, Jul 7, 2016 at 1:40 PM, Pete Muir < pmuir at redhat.com > > > wrote: > > > >> >> > > > >> >> > > > >> >> On 6 July 2016 at 20:02, Rick Wagner < rwagner at redhat.com > wrote: > > > >> >> > Hello DevTools, > > > >> >> > > > > >> >> > It seems we have a problem with the current version of the > > > >> >> > Development > > > >> >> > Suite > > > >> >> > installer. We have at least 2 new customer cases reporting > > inability > > > >> >> > to > > > >> >> > install due to the message dialogue "Terms and Conditions for > > the CDK > > > >> >> > have > > > >> >> > not been signed". > > > >> >> > > > > >> >> > This is concerning because we're also seeing similar activity on > > > >> >> > non-support > > > >> >> > channels. It's also worth noting that not every user that has a > > > >> >> > problem > > > >> >> > reports it-- some just give up and move on. There is enough > > volume > > > >> >> > here > > > >> >> > that we probably should treat this with some urgency. > > > >> >> > > > > >> >> > It seems likely the relevant code (thanks for highlighting this, > > > >> >> > Alexey) > > > >> >> > is > > > >> >> > below: > > > >> >> > > > > >> >> > ------------------------------------------------- > > > >> >> > > > > >> >> > login() { > > > >> >> > this.authFailed = false; > > > >> >> > this.tandcNotSigned = false; > > > >> >> > > > > >> >> > let req = { > > > >> >> > method: 'GET', > > > >> >> > url: > > > >> >> > ' > > > >> >> > > > https://developers.redhat.com/download-manager/rest/tc-accepted?downloadURL=/file/cdk-2.0.0-beta3.zip > > > >> >> > ', > > > >> >> > <<<<<<<<<---- returns 'false' when not approved > > > >> >> > > > >> >> I noticed when reading this that this code appears to be > > downloading > > > >> >> CDK 2.0.0-beta3 which implies that either this is an old version of > > > >> >> the installer, or the installer is installing a very old CDK... > > > >> >> > > > >> >> > headers: { > > > >> >> > 'Authorization': 'Basic ' + this.base64.encode(this.username + > > ':' + > > > >> >> > this.password) > > > >> >> > } > > > >> >> > }; > > > >> >> > > > > >> >> > this.http(req) > > > >> >> > .then(this.handleHttpSuccess.bind(this)) > > > >> >> > .catch(this.handleHttpFailure.bind(this)); > > > >> >> > } > > > >> >> > > > > >> >> > --------------------------------- > > > >> >> > > > > >> >> > > > > >> >> > So we have users getting denied use of our product. Do we > > require a > > > >> >> > rebuild > > > >> >> > immediately? Maybe. > > > >> >> > > > > >> >> > How about if we changed the rest service > > > >> >> > ( > > https://developers.redhat.com/download-manager/rest/tc-accepted ) > > > >> >> > so > > > >> >> > it > > > >> >> > includes a peak at an override database as well as whatever it's > > > >> >> > currently > > > >> >> > doing now? > > > >> >> > > > > >> >> > In that way, we could have the users pop over to a 'yes, I agree > > to > > > >> >> > the > > > >> >> > terms' page to insert an entry into the database. The rest > > service > > > >> >> > could > > > >> >> > use something like the provided username as a key to ensure a > > 'true' > > > >> >> > is > > > >> >> > returned. > > > >> >> > > > > >> >> > > > > >> >> > Or not. Is there a better way to fix this? > > > >> >> > > > > >> >> > Please consider, we need to fix this sooner rather than later.... > > > >> >> > > > > >> >> > Thanks, > > > >> >> > > > > >> >> > Rick > > > >> >> > > > > >> >> > > > > >> >> > _______________________________________________ > > > >> >> > 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 > > > >> >> > > > >> > > > > > > From lmohanty at redhat.com Thu Jul 21 11:25:12 2016 From: lmohanty at redhat.com (Lalatendu Mohanty) Date: Thu, 21 Jul 2016 16:55:12 +0530 Subject: [Devtools] docker-latest in ADB/CDK Message-ID: <48200cee-2e78-510d-cf2d-b3b671064ada@redhat.com> Hi, CentOS and RHEL is now providing docker-latest RPM along with regular docker package. Should we include it as part of ADB . IMO yes we should as it will give access to newer docker version to user if they need it. Also the question is what version of docker should be default installed in ADB? Let us know your thoughts. [1] http://mirror.centos.org/centos-7/7/extras/x86_64/Packages/docker-latest-1.10.3-44.el7.centos.x86_64.rpm Thanks, Lala From prkumar at redhat.com Thu Jul 21 11:45:37 2016 From: prkumar at redhat.com (Praveen Kumar) Date: Thu, 21 Jul 2016 17:15:37 +0530 Subject: [Devtools] docker-latest in ADB/CDK In-Reply-To: <48200cee-2e78-510d-cf2d-b3b671064ada@redhat.com> References: <48200cee-2e78-510d-cf2d-b3b671064ada@redhat.com> Message-ID: On Thu, Jul 21, 2016 at 4:55 PM, Lalatendu Mohanty wrote: > Hi, > > CentOS and RHEL is now providing docker-latest RPM along with regular docker > package. Should we include it as part of ADB . IMO yes we should as it will > give access to newer docker version to user if they need it. Also the > question is what version of docker should be default installed in ADB? AFAIK docker-latest we (as Red Hat) started building when docker broke some old API around images/registry so that user have choice to use accordingly. Currently if I check docker[0] and docker-latest[1] build both looks same but in future that may change (not sure). [0] https://brewweb.engineering.redhat.com/brew/packageinfo?packageID=13865 [1] https://brewweb.engineering.redhat.com/brew/packageinfo?packageID=57790 > > Let us know your thoughts. > > [1] > http://mirror.centos.org/centos-7/7/extras/x86_64/Packages/docker-latest-1.10.3-44.el7.centos.x86_64.rpm > > Thanks, > > Lala > > > _______________________________________________ > 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 Thu Jul 21 11:48:52 2016 From: lmohanty at redhat.com (Lalatendu Mohanty) Date: Thu, 21 Jul 2016 17:18:52 +0530 Subject: [Devtools] docker-latest in ADB/CDK In-Reply-To: References: <48200cee-2e78-510d-cf2d-b3b671064ada@redhat.com> Message-ID: On 07/21/2016 05:15 PM, Praveen Kumar wrote: > On Thu, Jul 21, 2016 at 4:55 PM, Lalatendu Mohanty wrote: >> Hi, >> >> CentOS and RHEL is now providing docker-latest RPM along with regular docker >> package. Should we include it as part of ADB . IMO yes we should as it will >> give access to newer docker version to user if they need it. Also the >> question is what version of docker should be default installed in ADB? > AFAIK docker-latest we (as Red Hat) started building when docker broke > some old API around images/registry so that user have choice to use > accordingly. Currently if I check docker[0] and docker-latest[1] build > both looks same but in future that may change (not sure). AFAIK the plan to give newer version through docker-latest, so that it will helps users to migrate production to newer version as they can try the newer version and see it breaks stuff. > [0] https://brewweb.engineering.redhat.com/brew/packageinfo?packageID=13865 > [1] https://brewweb.engineering.redhat.com/brew/packageinfo?packageID=57790 > >> Let us know your thoughts. >> >> [1] >> http://mirror.centos.org/centos-7/7/extras/x86_64/Packages/docker-latest-1.10.3-44.el7.centos.x86_64.rpm >> >> Thanks, >> >> Lala >> >> >> _______________________________________________ >> Devtools mailing list >> Devtools at redhat.com >> https://www.redhat.com/mailman/listinfo/devtools > > From kbsingh at redhat.com Thu Jul 21 11:52:06 2016 From: kbsingh at redhat.com (Karanbir Singh) Date: Thu, 21 Jul 2016 12:52:06 +0100 Subject: [Devtools] docker-latest in ADB/CDK In-Reply-To: <48200cee-2e78-510d-cf2d-b3b671064ada@redhat.com> References: <48200cee-2e78-510d-cf2d-b3b671064ada@redhat.com> Message-ID: -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 21/07/16 12:25, Lalatendu Mohanty wrote: > Hi, > > CentOS and RHEL is now providing docker-latest RPM along with > regular docker package. Should we include it as part of ADB . IMO > yes we should as it will give access to newer docker version to > user if they need it. Also the question is what version of docker > should be default installed in ADB? > > Let us know your thoughts. > > [1] > http://mirror.centos.org/centos-7/7/extras/x86_64/Packages/docker-late st-1.10.3-44.el7.centos.x86_64.rpm > > What is the user engagement around ADB ? do we know who they are and what they are doing with ADB ? - -- Karanbir Singh, Project Lead, The CentOS Project, London, UK Red Hat Ext. 8274455 | DID: 0044 207 009 4455 -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (GNU/Linux) iQEcBAEBAgAGBQJXkLdmAAoJEI3Oi2Mx7xbtLxEIAKtjJm3kQvM3m9kSDZE7Ra2q cHdorAAttEQFVlbkJaS7j0voauB4NNknJ2KhUlI08hQUYYval7Dtrv24lUwqNqEH rDubrsXSDjbC3GKXdDV3HCuaZb+vsrazZ1ugQFxN42Q6zTb+ZnNKgAehmyFRXHzO Nu0YpdxACuujCgvvDHJA1Q3QtQfoN58AbQBLMeTwXgubk8mCxTIfc24yTcQ/9aHh 8fEC9H9Tafno7yBVkZLuTlqa3WwrPfRo/gn7RRhF3ZDGx6TgCbN1jOG4nUjt1nxL 1ddYoWTsNZssP4hBexAWTbwkR2bbe4UGD+U26XIO/s704aTphdQV1h2BDFNMap8= =Ri7N -----END PGP SIGNATURE----- From kbsingh at redhat.com Thu Jul 21 11:54:29 2016 From: kbsingh at redhat.com (Karanbir Singh) Date: Thu, 21 Jul 2016 12:54:29 +0100 Subject: [Devtools] docker-latest in ADB/CDK In-Reply-To: References: <48200cee-2e78-510d-cf2d-b3b671064ada@redhat.com> Message-ID: <2d9c45e4-d3c6-6a0b-4d10-90a34177bb77@redhat.com> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 21/07/16 12:48, Lalatendu Mohanty wrote: > AFAIK the plan to give newer version through docker-latest, so that > it will helps users to migrate production to newer version as they > can try the newer version and see it breaks stuff. correct. also docker-latest may or maynot ( most likely will not for the immediate path ahead ) work with any of the integrated services or products on top of docker itself, shipped in the EL codebase - the target for those will remain docker itself. - -- Karanbir Singh, Project Lead, The CentOS Project, London, UK Red Hat Ext. 8274455 | DID: 0044 207 009 4455 -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (GNU/Linux) iQEcBAEBAgAGBQJXkLf1AAoJEI3Oi2Mx7xbtKvMIAI0TOhp54b+j4S6jlURD74XA AlqJTZE60WhBw5HfVdvDrSarIVkEsQ1bRhLbHqdM5dS845iQy197BEkCmfcVzlc2 QRwklIbhgPaxWPb4ua+8Arj27qy7QqQOMa4D8/tXDnBVnHh6Usx9A2YzMuoaK914 z7jBM50nbx7wWcHd2ViZ19A59Z/kf1f0GC+H0zAvIQzz9Qzh4s978sQBMR95c4rG M1dbdl7KAg+RIFHPWXAhU1r9pZfrHFBFymnoWicR8DaPXmGtgbXGFvO9yp4xdA8F Llk5ycfN9kh7ifEn9a5XtPZS3Vu24+Y8UrNL+nxT2c40vbuMVFXghr6E6xgU5Gk= =nHfJ -----END PGP SIGNATURE----- From bsutter at redhat.com Thu Jul 21 18:45:07 2016 From: bsutter at redhat.com (Burr Sutter) Date: Thu, 21 Jul 2016 14:45:07 -0400 Subject: [Devtools] Fwd: [openshift-sme] Blog post on Debugging Java Application with the CDK In-Reply-To: References: Message-ID: FYI ---------- Forwarded message ---------- From: Andrew Block Date: Thu, Jul 21, 2016 at 2:26 PM Subject: [openshift-sme] Blog post on Debugging Java Application with the CDK To: openshift-sme Wrote an article on how to debug Java application running in OpenShift in the Red Hat Container Development Kit (CDK). This demonstrates a good workflow for developers to follow when developing containerized applications for deployment in OpenShift utilizing their local environment. http://developers.redhat.com/blog/2016/07/21/debugging-java-applications-using-the-red-hat-container-development-kit/ Enjoy! Andrew Block Red Hat Consulting 101 N. Wacker, Suite 150 Chicago, IL 60606 andrew.block at redhat.com | m. (716) 870-2408 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 rwagner at redhat.com Thu Jul 21 19:54:01 2016 From: rwagner at redhat.com (Rick Wagner) Date: Thu, 21 Jul 2016 14:54:01 -0500 Subject: [Devtools] C/O CDK SMEs: Windows user going off the rails somewhere along the line Message-ID: Hello CDK SMEs, We have a support case where the user is unable to use the CDK. They have installed via Development Suite installer and offer the following: ------------------------------------------------- I installed the Suite and tried to start the server Container Development Environment and it seems it started successfully (i attached log on file vagrant_up.txt). But I received this error after server started: "Unable to configure docker and openshift. Calls to vagrant service-manager are returning empty environments." -------------------------------------------------- We've compared the vagrant log to a lab machine known to work, we see a difference starting with vagrant-registration's actions. (See screenshot below.) A comparison of the vagrant plug-ins shows the user has the same versions the lab box has. The Eclipse log offers us the following. Note especially the curious phrase "Calls to vagrant service-manager are returning empty environments.". ------------------------------------------------------ !ENTRY org.jboss.tools.openshift.cdk.server 4 0 2016-07-21 09:48:26.869 !MESSAGE Unable to successfully complete a call to vagrant service-manager. !STACK 0 java.util.concurrent.TimeoutException: Process output: ^[[0m # docker env:^[[0m # Set the following environment variables to enable access to the # docker daemon running inside of the vagrant virtual machine: export DOCKER_HOST=tcp://10.1.2.2:2376 export DOCKER_CERT_PATH='C:\Pedro\Software\Openshift_RHCDK_suite10\cdk\components\rhel\rhel-ose\.vagrant\machines\default\virtualbox\docker\' export DOCKER_TLS_VERIFY=1 export DOCKER_API_VERSION=1.21 ^[[0m^[[0m ^[[0m # openshift env:^[[0m ^[[0m# You can access the OpenShift console on: https://10.1.2.2:8443/console # To use OpenShift CLI, run: oc login https://10.1.2.2:8443 export OPENSHIFT_URL=https://10.1.2.2:8443 export OPENSHIFT_WEB_CONSOLE=https://10.1.2.2:8443/console export DOCKER_REGISTRY=hub.openshift.rhel-cdk.10.1.2.2.xip.io^[[0m ^[[0m # run following command to configure your shell: # eval "$(VAGRANT_NO_COLOR=1 vagrant service-manager env | tr -d '\r')"^[[0m at org.jboss.tools.openshift.cdk.server.core.internal.adapter.controllers.VagrantLaunchUtility.call(VagrantLaunchUtility.java:186) at org.jboss.tools.openshift.cdk.server.core.internal.adapter.controllers.VagrantLaunchUtility.call(VagrantLaunchUtility.java:153) at org.jboss.tools.openshift.cdk.server.core.internal.listeners.ServiceManagerEnvironment.loadServiceManagerEnvironment(ServiceManagerEnvironment.java:108) at org.jboss.tools.openshift.cdk.server.core.internal.listeners.ServiceManagerEnvironment.loadServiceManagerEnvironment(ServiceManagerEnvironment.java:85) at org.jboss.tools.openshift.cdk.server.core.internal.listeners.ServiceManagerEnvironment.getOrLoadServiceManagerEnvironment(ServiceManagerEnvironment.java:67) at org.jboss.tools.openshift.cdk.server.core.internal.listeners.ServiceManagerEnvironment.getOrLoadServiceManagerEnvironment(ServiceManagerEnvironment.java:59) at org.jboss.tools.openshift.cdk.server.core.internal.adapter.VagrantPoller.checkOpenShiftHealth(VagrantPoller.java:185) at org.jboss.tools.openshift.cdk.server.core.internal.adapter.VagrantPoller.onePing(VagrantPoller.java:174) at org.jboss.tools.openshift.cdk.server.core.internal.adapter.VagrantPoller.onePingSafe(VagrantPoller.java:154) at org.jboss.tools.openshift.cdk.server.core.internal.adapter.VagrantPoller.getCurrentStateSynchronous(VagrantPoller.java:133) at org.jboss.tools.openshift.cdk.server.core.internal.adapter.controllers.CDKLaunchController.handleProcessTerminated(CDKLaunchController.java:250) at org.jboss.tools.openshift.cdk.server.core.internal.adapter.controllers.CDKLaunchController.access$2(CDKLaunchController.java:242) at org.jboss.tools.openshift.cdk.server.core.internal.adapter.controllers.CDKLaunchController$2.run(CDKLaunchController.java:235) !ENTRY org.jboss.tools.openshift.cdk.server 4 0 2016-07-21 09:49:07.139 !MESSAGE Unable to successfully complete a call to vagrant service-manager. !STACK 0 java.util.concurrent.TimeoutException: Process output: ^[[0m # docker env:^[[0m # Set the following environment variables to enable access to the # docker daemon running inside of the vagrant virtual machine: export DOCKER_HOST=tcp://10.1.2.2:2376 export DOCKER_CERT_PATH='C:\Pedro\Software\Openshift_RHCDK_suite10\cdk\components\rhel\rhel-ose\.vagrant\machines\default\virtualbox\docker\' export DOCKER_TLS_VERIFY=1 export DOCKER_API_VERSION=1.21 ^[[0m^[[0m ^[[0m # openshift env:^[[0m ^[[0m# You can access the OpenShift console on: https://10.1.2.2:8443/console # To use OpenShift CLI, run: oc login https://10.1.2.2:8443 export OPENSHIFT_URL=https://10.1.2.2:8443 export OPENSHIFT_WEB_CONSOLE=https://10.1.2.2:8443/console export DOCKER_REGISTRY=hub.openshift.rhel-cdk.10.1.2.2.xip.io^[[0m ^[[0m # run following command to configure your shell: # eval "$(VAGRANT_NO_COLOR=1 vagrant service-manager env | tr -d '\r')"^[[0m at org.jboss.tools.openshift.cdk.server.core.internal.adapter.controllers.VagrantLaunchUtility.call(VagrantLaunchUtility.java:186) at org.jboss.tools.openshift.cdk.server.core.internal.adapter.controllers.VagrantLaunchUtility.call(VagrantLaunchUtility.java:153) at org.jboss.tools.openshift.cdk.server.core.internal.listeners.ServiceManagerEnvironment.loadServiceManagerEnvironment(ServiceManagerEnvironment.java:108) at org.jboss.tools.openshift.cdk.server.core.internal.listeners.ServiceManagerEnvironment.loadServiceManagerEnvironment(ServiceManagerEnvironment.java:85) at org.jboss.tools.openshift.cdk.server.core.internal.listeners.ServiceManagerEnvironment.getOrLoadServiceManagerEnvironment(ServiceManagerEnvironment.java:67) at org.jboss.tools.openshift.cdk.server.core.internal.listeners.ServiceManagerEnvironment.getOrLoadServiceManagerEnvironment(ServiceManagerEnvironment.java:59) at org.jboss.tools.openshift.cdk.server.core.internal.listeners.ConfigureDependentFrameworksListener.configureFrameworks(ConfigureDependentFrameworksListener.java:53) at org.jboss.tools.openshift.cdk.server.core.internal.listeners.ConfigureDependentFrameworksListener$1.run(ConfigureDependentFrameworksListener.java:43) at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55) !ENTRY org.jboss.tools.openshift.cdk.server.core 4 0 2016-07-21 09:49:07.142 !MESSAGE Unable to configure docker and openshift. Calls to vagrant service-manager are returning empty environments. -------------------------------------------------------------------------------------- Any suggestions are greatly appreciated. Thanks, Rick [image: Inline image 2] -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image.png Type: image/png Size: 246410 bytes Desc: not available URL: From jmaury at redhat.com Fri Jul 22 07:46:08 2016 From: jmaury at redhat.com (Jean-Francois Maury) Date: Fri, 22 Jul 2016 09:46:08 +0200 Subject: [Devtools] C/O CDK SMEs: Windows user going off the rails somewhere along the line In-Reply-To: References: Message-ID: Rick, we have found an issue regarding the output of vagrant-registration being corrupted by escape characters. We've fixed and it will be included in this Sprint bits of DevStudio. There is a possible workaround: define the env variable (on Windows using the Control Panel) VAGRANT_NO_COLOR and set the value to 1. I would suggest rebooting your machine and launch DevStudio again. Jeff On Thu, Jul 21, 2016 at 9:54 PM, Rick Wagner wrote: > Hello CDK SMEs, > > We have a support case where the user is unable to use the CDK. They have > installed via Development Suite installer and offer the following: > > ------------------------------------------------- > I installed the Suite and tried to start the server Container Development > Environment and it seems it started successfully (i attached log on file > vagrant_up.txt). But I received this error after server started: "Unable > to configure docker and openshift. Calls to vagrant service-manager are > returning empty environments." > -------------------------------------------------- > > > We've compared the vagrant log to a lab machine known to work, we see a > difference starting with vagrant-registration's actions. (See screenshot > below.) > > A comparison of the vagrant plug-ins shows the user has the same versions > the lab box has. > > The Eclipse log offers us the following. Note especially the curious > phrase "Calls to vagrant service-manager are returning empty environments.". > > ------------------------------------------------------ > !ENTRY org.jboss.tools.openshift.cdk.server 4 0 2016-07-21 09:48:26.869 > !MESSAGE Unable to successfully complete a call to vagrant service-manager. > !STACK 0 > java.util.concurrent.TimeoutException: Process output: > ^[[0m # docker env:^[[0m # Set the following environment variables > to enable access to the # docker daemon running inside of the vagrant > virtual machine: export DOCKER_HOST=tcp://10.1.2.2:2376 export > DOCKER_CERT_PATH='C:\Pedro\Software\Openshift_RHCDK_suite10\cdk\components\rhel\rhel-ose\.vagrant\machines\default\virtualbox\docker\' > export DOCKER_TLS_VERIFY=1 export DOCKER_API_VERSION=1.21 ^[[0m^[[0m > ^[[0m # openshift env:^[[0m ^[[0m# You can access the OpenShift console > on: https://10.1.2.2:8443/console # To use OpenShift CLI, run: oc login > https://10.1.2.2:8443 export OPENSHIFT_URL=https://10.1.2.2:8443 > export OPENSHIFT_WEB_CONSOLE=https://10.1.2.2:8443/console export > DOCKER_REGISTRY=hub.openshift.rhel-cdk.10.1.2.2.xip.io^[[0m ^[[0m # > run following command to configure your shell: # eval > "$(VAGRANT_NO_COLOR=1 vagrant service-manager env | tr -d '\r')"^[[0m > at > org.jboss.tools.openshift.cdk.server.core.internal.adapter.controllers.VagrantLaunchUtility.call(VagrantLaunchUtility.java:186) > at > org.jboss.tools.openshift.cdk.server.core.internal.adapter.controllers.VagrantLaunchUtility.call(VagrantLaunchUtility.java:153) > at > org.jboss.tools.openshift.cdk.server.core.internal.listeners.ServiceManagerEnvironment.loadServiceManagerEnvironment(ServiceManagerEnvironment.java:108) > at > org.jboss.tools.openshift.cdk.server.core.internal.listeners.ServiceManagerEnvironment.loadServiceManagerEnvironment(ServiceManagerEnvironment.java:85) > at > org.jboss.tools.openshift.cdk.server.core.internal.listeners.ServiceManagerEnvironment.getOrLoadServiceManagerEnvironment(ServiceManagerEnvironment.java:67) > at > org.jboss.tools.openshift.cdk.server.core.internal.listeners.ServiceManagerEnvironment.getOrLoadServiceManagerEnvironment(ServiceManagerEnvironment.java:59) > at > org.jboss.tools.openshift.cdk.server.core.internal.adapter.VagrantPoller.checkOpenShiftHealth(VagrantPoller.java:185) > at > org.jboss.tools.openshift.cdk.server.core.internal.adapter.VagrantPoller.onePing(VagrantPoller.java:174) > at > org.jboss.tools.openshift.cdk.server.core.internal.adapter.VagrantPoller.onePingSafe(VagrantPoller.java:154) > at > org.jboss.tools.openshift.cdk.server.core.internal.adapter.VagrantPoller.getCurrentStateSynchronous(VagrantPoller.java:133) > at > org.jboss.tools.openshift.cdk.server.core.internal.adapter.controllers.CDKLaunchController.handleProcessTerminated(CDKLaunchController.java:250) > at > org.jboss.tools.openshift.cdk.server.core.internal.adapter.controllers.CDKLaunchController.access$2(CDKLaunchController.java:242) > at > org.jboss.tools.openshift.cdk.server.core.internal.adapter.controllers.CDKLaunchController$2.run(CDKLaunchController.java:235) > > !ENTRY org.jboss.tools.openshift.cdk.server 4 0 2016-07-21 09:49:07.139 > !MESSAGE Unable to successfully complete a call to vagrant service-manager. > !STACK 0 > java.util.concurrent.TimeoutException: Process output: > ^[[0m # docker env:^[[0m # Set the following environment variables > to enable access to the # docker daemon running inside of the vagrant > virtual machine: export DOCKER_HOST=tcp://10.1.2.2:2376 export > DOCKER_CERT_PATH='C:\Pedro\Software\Openshift_RHCDK_suite10\cdk\components\rhel\rhel-ose\.vagrant\machines\default\virtualbox\docker\' > export DOCKER_TLS_VERIFY=1 export DOCKER_API_VERSION=1.21 ^[[0m^[[0m > ^[[0m # openshift env:^[[0m ^[[0m# You can access the OpenShift console > on: https://10.1.2.2:8443/console # To use OpenShift CLI, run: oc login > https://10.1.2.2:8443 export OPENSHIFT_URL=https://10.1.2.2:8443 > export OPENSHIFT_WEB_CONSOLE=https://10.1.2.2:8443/console export > DOCKER_REGISTRY=hub.openshift.rhel-cdk.10.1.2.2.xip.io^[[0m ^[[0m # > run following command to configure your shell: # eval > "$(VAGRANT_NO_COLOR=1 vagrant service-manager env | tr -d '\r')"^[[0m > at > org.jboss.tools.openshift.cdk.server.core.internal.adapter.controllers.VagrantLaunchUtility.call(VagrantLaunchUtility.java:186) > at > org.jboss.tools.openshift.cdk.server.core.internal.adapter.controllers.VagrantLaunchUtility.call(VagrantLaunchUtility.java:153) > at > org.jboss.tools.openshift.cdk.server.core.internal.listeners.ServiceManagerEnvironment.loadServiceManagerEnvironment(ServiceManagerEnvironment.java:108) > at > org.jboss.tools.openshift.cdk.server.core.internal.listeners.ServiceManagerEnvironment.loadServiceManagerEnvironment(ServiceManagerEnvironment.java:85) > at > org.jboss.tools.openshift.cdk.server.core.internal.listeners.ServiceManagerEnvironment.getOrLoadServiceManagerEnvironment(ServiceManagerEnvironment.java:67) > at > org.jboss.tools.openshift.cdk.server.core.internal.listeners.ServiceManagerEnvironment.getOrLoadServiceManagerEnvironment(ServiceManagerEnvironment.java:59) > at > org.jboss.tools.openshift.cdk.server.core.internal.listeners.ConfigureDependentFrameworksListener.configureFrameworks(ConfigureDependentFrameworksListener.java:53) > at > org.jboss.tools.openshift.cdk.server.core.internal.listeners.ConfigureDependentFrameworksListener$1.run(ConfigureDependentFrameworksListener.java:43) > at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55) > > !ENTRY org.jboss.tools.openshift.cdk.server.core 4 0 2016-07-21 > 09:49:07.142 > !MESSAGE Unable to configure docker and openshift. Calls to vagrant > service-manager are returning empty environments. > > > -------------------------------------------------------------------------------------- > > > > > Any suggestions are greatly appreciated. > > Thanks, > > Rick > > > > > > > [image: Inline image 2] > > _______________________________________________ > Devtools mailing list > Devtools at redhat.com > https://www.redhat.com/mailman/listinfo/devtools > > -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image.png Type: image/png Size: 246410 bytes Desc: not available URL: From rwagner at redhat.com Fri Jul 22 12:27:30 2016 From: rwagner at redhat.com (Rick Wagner) Date: Fri, 22 Jul 2016 07:27:30 -0500 Subject: [Devtools] C/O CDK SMEs: Windows user going off the rails somewhere along the line In-Reply-To: References: Message-ID: Many thanks, Jeff. We'll ask our customer to try this workaround. (We'll document it in KCS for later usage, also.) Rick On Fri, Jul 22, 2016 at 2:46 AM, Jean-Francois Maury wrote: > Rick, > > we have found an issue regarding the output of vagrant-registration being > corrupted by escape characters. We've fixed and it will be included in this > Sprint bits of DevStudio. > There is a possible workaround: define the env variable (on Windows using > the Control Panel) VAGRANT_NO_COLOR and set the value to 1. I would suggest > rebooting your machine and launch DevStudio again. > > Jeff > > On Thu, Jul 21, 2016 at 9:54 PM, Rick Wagner wrote: > >> Hello CDK SMEs, >> >> We have a support case where the user is unable to use the CDK. They >> have installed via Development Suite installer and offer the following: >> >> ------------------------------------------------- >> I installed the Suite and tried to start the server Container Development >> Environment and it seems it started successfully (i attached log on file >> vagrant_up.txt). But I received this error after server started: "Unable >> to configure docker and openshift. Calls to vagrant service-manager are >> returning empty environments." >> -------------------------------------------------- >> >> >> We've compared the vagrant log to a lab machine known to work, we see a >> difference starting with vagrant-registration's actions. (See screenshot >> below.) >> >> A comparison of the vagrant plug-ins shows the user has the same versions >> the lab box has. >> >> The Eclipse log offers us the following. Note especially the curious >> phrase "Calls to vagrant service-manager are returning empty environments.". >> >> ------------------------------------------------------ >> !ENTRY org.jboss.tools.openshift.cdk.server 4 0 2016-07-21 09:48:26.869 >> !MESSAGE Unable to successfully complete a call to vagrant >> service-manager. >> !STACK 0 >> java.util.concurrent.TimeoutException: Process output: >> ^[[0m # docker env:^[[0m # Set the following environment variables >> to enable access to the # docker daemon running inside of the vagrant >> virtual machine: export DOCKER_HOST=tcp://10.1.2.2:2376 export >> DOCKER_CERT_PATH='C:\Pedro\Software\Openshift_RHCDK_suite10\cdk\components\rhel\rhel-ose\.vagrant\machines\default\virtualbox\docker\' >> export DOCKER_TLS_VERIFY=1 export DOCKER_API_VERSION=1.21 ^[[0m^[[0m >> ^[[0m # openshift env:^[[0m ^[[0m# You can access the OpenShift console >> on: https://10.1.2.2:8443/console # To use OpenShift CLI, run: oc >> login https://10.1.2.2:8443 export OPENSHIFT_URL=https://10.1.2.2:8443 >> export OPENSHIFT_WEB_CONSOLE=https://10.1.2.2:8443/console export >> DOCKER_REGISTRY=hub.openshift.rhel-cdk.10.1.2.2.xip.io^[[0m ^[[0m # >> run following command to configure your shell: # eval >> "$(VAGRANT_NO_COLOR=1 vagrant service-manager env | tr -d '\r')"^[[0m >> at >> org.jboss.tools.openshift.cdk.server.core.internal.adapter.controllers.VagrantLaunchUtility.call(VagrantLaunchUtility.java:186) >> at >> org.jboss.tools.openshift.cdk.server.core.internal.adapter.controllers.VagrantLaunchUtility.call(VagrantLaunchUtility.java:153) >> at >> org.jboss.tools.openshift.cdk.server.core.internal.listeners.ServiceManagerEnvironment.loadServiceManagerEnvironment(ServiceManagerEnvironment.java:108) >> at >> org.jboss.tools.openshift.cdk.server.core.internal.listeners.ServiceManagerEnvironment.loadServiceManagerEnvironment(ServiceManagerEnvironment.java:85) >> at >> org.jboss.tools.openshift.cdk.server.core.internal.listeners.ServiceManagerEnvironment.getOrLoadServiceManagerEnvironment(ServiceManagerEnvironment.java:67) >> at >> org.jboss.tools.openshift.cdk.server.core.internal.listeners.ServiceManagerEnvironment.getOrLoadServiceManagerEnvironment(ServiceManagerEnvironment.java:59) >> at >> org.jboss.tools.openshift.cdk.server.core.internal.adapter.VagrantPoller.checkOpenShiftHealth(VagrantPoller.java:185) >> at >> org.jboss.tools.openshift.cdk.server.core.internal.adapter.VagrantPoller.onePing(VagrantPoller.java:174) >> at >> org.jboss.tools.openshift.cdk.server.core.internal.adapter.VagrantPoller.onePingSafe(VagrantPoller.java:154) >> at >> org.jboss.tools.openshift.cdk.server.core.internal.adapter.VagrantPoller.getCurrentStateSynchronous(VagrantPoller.java:133) >> at >> org.jboss.tools.openshift.cdk.server.core.internal.adapter.controllers.CDKLaunchController.handleProcessTerminated(CDKLaunchController.java:250) >> at >> org.jboss.tools.openshift.cdk.server.core.internal.adapter.controllers.CDKLaunchController.access$2(CDKLaunchController.java:242) >> at >> org.jboss.tools.openshift.cdk.server.core.internal.adapter.controllers.CDKLaunchController$2.run(CDKLaunchController.java:235) >> >> !ENTRY org.jboss.tools.openshift.cdk.server 4 0 2016-07-21 09:49:07.139 >> !MESSAGE Unable to successfully complete a call to vagrant >> service-manager. >> !STACK 0 >> java.util.concurrent.TimeoutException: Process output: >> ^[[0m # docker env:^[[0m # Set the following environment variables >> to enable access to the # docker daemon running inside of the vagrant >> virtual machine: export DOCKER_HOST=tcp://10.1.2.2:2376 export >> DOCKER_CERT_PATH='C:\Pedro\Software\Openshift_RHCDK_suite10\cdk\components\rhel\rhel-ose\.vagrant\machines\default\virtualbox\docker\' >> export DOCKER_TLS_VERIFY=1 export DOCKER_API_VERSION=1.21 ^[[0m^[[0m >> ^[[0m # openshift env:^[[0m ^[[0m# You can access the OpenShift console >> on: https://10.1.2.2:8443/console # To use OpenShift CLI, run: oc >> login https://10.1.2.2:8443 export OPENSHIFT_URL=https://10.1.2.2:8443 >> export OPENSHIFT_WEB_CONSOLE=https://10.1.2.2:8443/console export >> DOCKER_REGISTRY=hub.openshift.rhel-cdk.10.1.2.2.xip.io^[[0m ^[[0m # >> run following command to configure your shell: # eval >> "$(VAGRANT_NO_COLOR=1 vagrant service-manager env | tr -d '\r')"^[[0m >> at >> org.jboss.tools.openshift.cdk.server.core.internal.adapter.controllers.VagrantLaunchUtility.call(VagrantLaunchUtility.java:186) >> at >> org.jboss.tools.openshift.cdk.server.core.internal.adapter.controllers.VagrantLaunchUtility.call(VagrantLaunchUtility.java:153) >> at >> org.jboss.tools.openshift.cdk.server.core.internal.listeners.ServiceManagerEnvironment.loadServiceManagerEnvironment(ServiceManagerEnvironment.java:108) >> at >> org.jboss.tools.openshift.cdk.server.core.internal.listeners.ServiceManagerEnvironment.loadServiceManagerEnvironment(ServiceManagerEnvironment.java:85) >> at >> org.jboss.tools.openshift.cdk.server.core.internal.listeners.ServiceManagerEnvironment.getOrLoadServiceManagerEnvironment(ServiceManagerEnvironment.java:67) >> at >> org.jboss.tools.openshift.cdk.server.core.internal.listeners.ServiceManagerEnvironment.getOrLoadServiceManagerEnvironment(ServiceManagerEnvironment.java:59) >> at >> org.jboss.tools.openshift.cdk.server.core.internal.listeners.ConfigureDependentFrameworksListener.configureFrameworks(ConfigureDependentFrameworksListener.java:53) >> at >> org.jboss.tools.openshift.cdk.server.core.internal.listeners.ConfigureDependentFrameworksListener$1.run(ConfigureDependentFrameworksListener.java:43) >> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55) >> >> !ENTRY org.jboss.tools.openshift.cdk.server.core 4 0 2016-07-21 >> 09:49:07.142 >> !MESSAGE Unable to configure docker and openshift. Calls to vagrant >> service-manager are returning empty environments. >> >> >> -------------------------------------------------------------------------------------- >> >> >> >> >> Any suggestions are greatly appreciated. >> >> Thanks, >> >> Rick >> >> >> >> >> >> >> [image: Inline image 2] >> >> _______________________________________________ >> Devtools mailing list >> Devtools at redhat.com >> https://www.redhat.com/mailman/listinfo/devtools >> >> > -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image.png Type: image/png Size: 246410 bytes Desc: not available URL: From tmancini at redhat.com Fri Jul 22 12:37:59 2016 From: tmancini at redhat.com (Todd Mancini) Date: Fri, 22 Jul 2016 08:37:59 -0400 Subject: [Devtools] C/O CDK SMEs: Windows user going off the rails somewhere along the line In-Reply-To: References: Message-ID: When you document it, please leave out the "and reboot" part, as that's a very dramatic solution to a much easier problem. The user simply needs to get the updated environment into their current context. I can help with the wording/instructions relative to that. On Fri, Jul 22, 2016 at 8:27 AM, Rick Wagner wrote: > Many thanks, Jeff. > > We'll ask our customer to try this workaround. (We'll document it in KCS > for later usage, also.) > > Rick > > On Fri, Jul 22, 2016 at 2:46 AM, Jean-Francois Maury > wrote: > >> Rick, >> >> we have found an issue regarding the output of vagrant-registration being >> corrupted by escape characters. We've fixed and it will be included in this >> Sprint bits of DevStudio. >> There is a possible workaround: define the env variable (on Windows using >> the Control Panel) VAGRANT_NO_COLOR and set the value to 1. I would suggest >> rebooting your machine and launch DevStudio again. >> >> Jeff >> >> On Thu, Jul 21, 2016 at 9:54 PM, Rick Wagner wrote: >> >>> Hello CDK SMEs, >>> >>> We have a support case where the user is unable to use the CDK. They >>> have installed via Development Suite installer and offer the following: >>> >>> ------------------------------------------------- >>> I installed the Suite and tried to start the server Container >>> Development Environment and it seems it started successfully (i attached >>> log on file vagrant_up.txt). But I received this error after server >>> started: "Unable to configure docker and openshift. Calls to vagrant >>> service-manager are returning empty environments." >>> -------------------------------------------------- >>> >>> >>> We've compared the vagrant log to a lab machine known to work, we see a >>> difference starting with vagrant-registration's actions. (See screenshot >>> below.) >>> >>> A comparison of the vagrant plug-ins shows the user has the same >>> versions the lab box has. >>> >>> The Eclipse log offers us the following. Note especially the curious >>> phrase "Calls to vagrant service-manager are returning empty environments.". >>> >>> ------------------------------------------------------ >>> !ENTRY org.jboss.tools.openshift.cdk.server 4 0 2016-07-21 09:48:26.869 >>> !MESSAGE Unable to successfully complete a call to vagrant >>> service-manager. >>> !STACK 0 >>> java.util.concurrent.TimeoutException: Process output: >>> ^[[0m # docker env:^[[0m # Set the following environment >>> variables to enable access to the # docker daemon running inside of the >>> vagrant virtual machine: export DOCKER_HOST=tcp://10.1.2.2:2376 >>> export >>> DOCKER_CERT_PATH='C:\Pedro\Software\Openshift_RHCDK_suite10\cdk\components\rhel\rhel-ose\.vagrant\machines\default\virtualbox\docker\' >>> export DOCKER_TLS_VERIFY=1 export DOCKER_API_VERSION=1.21 ^[[0m^[[0m >>> ^[[0m # openshift env:^[[0m ^[[0m# You can access the OpenShift console >>> on: https://10.1.2.2:8443/console # To use OpenShift CLI, run: oc >>> login https://10.1.2.2:8443 export OPENSHIFT_URL=https://10.1.2.2:8443 >>> export OPENSHIFT_WEB_CONSOLE=https://10.1.2.2:8443/console export >>> DOCKER_REGISTRY=hub.openshift.rhel-cdk.10.1.2.2.xip.io^[[0m ^[[0m # >>> run following command to configure your shell: # eval >>> "$(VAGRANT_NO_COLOR=1 vagrant service-manager env | tr -d '\r')"^[[0m >>> at >>> org.jboss.tools.openshift.cdk.server.core.internal.adapter.controllers.VagrantLaunchUtility.call(VagrantLaunchUtility.java:186) >>> at >>> org.jboss.tools.openshift.cdk.server.core.internal.adapter.controllers.VagrantLaunchUtility.call(VagrantLaunchUtility.java:153) >>> at >>> org.jboss.tools.openshift.cdk.server.core.internal.listeners.ServiceManagerEnvironment.loadServiceManagerEnvironment(ServiceManagerEnvironment.java:108) >>> at >>> org.jboss.tools.openshift.cdk.server.core.internal.listeners.ServiceManagerEnvironment.loadServiceManagerEnvironment(ServiceManagerEnvironment.java:85) >>> at >>> org.jboss.tools.openshift.cdk.server.core.internal.listeners.ServiceManagerEnvironment.getOrLoadServiceManagerEnvironment(ServiceManagerEnvironment.java:67) >>> at >>> org.jboss.tools.openshift.cdk.server.core.internal.listeners.ServiceManagerEnvironment.getOrLoadServiceManagerEnvironment(ServiceManagerEnvironment.java:59) >>> at >>> org.jboss.tools.openshift.cdk.server.core.internal.adapter.VagrantPoller.checkOpenShiftHealth(VagrantPoller.java:185) >>> at >>> org.jboss.tools.openshift.cdk.server.core.internal.adapter.VagrantPoller.onePing(VagrantPoller.java:174) >>> at >>> org.jboss.tools.openshift.cdk.server.core.internal.adapter.VagrantPoller.onePingSafe(VagrantPoller.java:154) >>> at >>> org.jboss.tools.openshift.cdk.server.core.internal.adapter.VagrantPoller.getCurrentStateSynchronous(VagrantPoller.java:133) >>> at >>> org.jboss.tools.openshift.cdk.server.core.internal.adapter.controllers.CDKLaunchController.handleProcessTerminated(CDKLaunchController.java:250) >>> at >>> org.jboss.tools.openshift.cdk.server.core.internal.adapter.controllers.CDKLaunchController.access$2(CDKLaunchController.java:242) >>> at >>> org.jboss.tools.openshift.cdk.server.core.internal.adapter.controllers.CDKLaunchController$2.run(CDKLaunchController.java:235) >>> >>> !ENTRY org.jboss.tools.openshift.cdk.server 4 0 2016-07-21 09:49:07.139 >>> !MESSAGE Unable to successfully complete a call to vagrant >>> service-manager. >>> !STACK 0 >>> java.util.concurrent.TimeoutException: Process output: >>> ^[[0m # docker env:^[[0m # Set the following environment >>> variables to enable access to the # docker daemon running inside of the >>> vagrant virtual machine: export DOCKER_HOST=tcp://10.1.2.2:2376 >>> export >>> DOCKER_CERT_PATH='C:\Pedro\Software\Openshift_RHCDK_suite10\cdk\components\rhel\rhel-ose\.vagrant\machines\default\virtualbox\docker\' >>> export DOCKER_TLS_VERIFY=1 export DOCKER_API_VERSION=1.21 ^[[0m^[[0m >>> ^[[0m # openshift env:^[[0m ^[[0m# You can access the OpenShift console >>> on: https://10.1.2.2:8443/console # To use OpenShift CLI, run: oc >>> login https://10.1.2.2:8443 export OPENSHIFT_URL=https://10.1.2.2:8443 >>> export OPENSHIFT_WEB_CONSOLE=https://10.1.2.2:8443/console export >>> DOCKER_REGISTRY=hub.openshift.rhel-cdk.10.1.2.2.xip.io^[[0m ^[[0m # >>> run following command to configure your shell: # eval >>> "$(VAGRANT_NO_COLOR=1 vagrant service-manager env | tr -d '\r')"^[[0m >>> at >>> org.jboss.tools.openshift.cdk.server.core.internal.adapter.controllers.VagrantLaunchUtility.call(VagrantLaunchUtility.java:186) >>> at >>> org.jboss.tools.openshift.cdk.server.core.internal.adapter.controllers.VagrantLaunchUtility.call(VagrantLaunchUtility.java:153) >>> at >>> org.jboss.tools.openshift.cdk.server.core.internal.listeners.ServiceManagerEnvironment.loadServiceManagerEnvironment(ServiceManagerEnvironment.java:108) >>> at >>> org.jboss.tools.openshift.cdk.server.core.internal.listeners.ServiceManagerEnvironment.loadServiceManagerEnvironment(ServiceManagerEnvironment.java:85) >>> at >>> org.jboss.tools.openshift.cdk.server.core.internal.listeners.ServiceManagerEnvironment.getOrLoadServiceManagerEnvironment(ServiceManagerEnvironment.java:67) >>> at >>> org.jboss.tools.openshift.cdk.server.core.internal.listeners.ServiceManagerEnvironment.getOrLoadServiceManagerEnvironment(ServiceManagerEnvironment.java:59) >>> at >>> org.jboss.tools.openshift.cdk.server.core.internal.listeners.ConfigureDependentFrameworksListener.configureFrameworks(ConfigureDependentFrameworksListener.java:53) >>> at >>> org.jboss.tools.openshift.cdk.server.core.internal.listeners.ConfigureDependentFrameworksListener$1.run(ConfigureDependentFrameworksListener.java:43) >>> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55) >>> >>> !ENTRY org.jboss.tools.openshift.cdk.server.core 4 0 2016-07-21 >>> 09:49:07.142 >>> !MESSAGE Unable to configure docker and openshift. Calls to vagrant >>> service-manager are returning empty environments. >>> >>> >>> -------------------------------------------------------------------------------------- >>> >>> >>> >>> >>> Any suggestions are greatly appreciated. >>> >>> Thanks, >>> >>> Rick >>> >>> >>> >>> >>> >>> >>> [image: Inline image 2] >>> >>> _______________________________________________ >>> 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: -------------- next part -------------- A non-text attachment was scrubbed... Name: image.png Type: image/png Size: 246410 bytes Desc: not available URL: From mlabuda at redhat.com Mon Jul 25 09:20:19 2016 From: mlabuda at redhat.com (Marian Labuda) Date: Mon, 25 Jul 2016 11:20:19 +0200 Subject: [Devtools] Fwd: [openshift-sme] Blog post on Debugging Java Application with the CDK In-Reply-To: References: Message-ID: Nice, Just 2 notes (I did not read it whole, just a quick overview). I've spotted in section "Using Red Hat JBoss Developer Studio to Connect to OpenShift" that right double quotes are not rendered correctly. See: Once complete, a connection called ?openshift-dev https://10.1.2.2:8443” Second is just a thought. In the article is debugging done via starting port forwarding and connecting remote java application. In tooling we have much more sophisticated way to start debugging. OpenShift 3 Server Adapter contains a context menu item Debug. Click on the item adds debug port specs to deployment configuration, starts port forwarding and even attaches a remote java application. From running application to being debugged application in one click, if you omit steps to create a server adapter. To create an OS 3 server adapter just select a service in OpenShift explorer view and select Server Adapter. It opens wizard with preselected Eclipse workspace project, OpenShift service etc. So in this way you can create an adapter just by click on the Finish button. Mari?n Labuda JBoss JBDS QE On Thu, Jul 21, 2016 at 8:45 PM, Burr Sutter wrote: > FYI > > ---------- Forwarded message ---------- > From: Andrew Block > Date: Thu, Jul 21, 2016 at 2:26 PM > Subject: [openshift-sme] Blog post on Debugging Java Application with the > CDK > To: openshift-sme > > > Wrote an article on how to debug Java application running in OpenShift in > the Red Hat Container Development Kit (CDK). This demonstrates a good > workflow for developers to follow when developing containerized > applications for deployment in OpenShift utilizing their local environment. > > > http://developers.redhat.com/blog/2016/07/21/debugging-java-applications-using-the-red-hat-container-development-kit/ > > > Enjoy! > > > Andrew Block > Red Hat Consulting > 101 N. Wacker, Suite 150 > Chicago, IL 60606 > andrew.block at redhat.com | m. (716) 870-2408 > > 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 > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From lmohanty at redhat.com Mon Jul 25 09:25:26 2016 From: lmohanty at redhat.com (Lalatendu Mohanty) Date: Mon, 25 Jul 2016 14:55:26 +0530 Subject: [Devtools] docker-latest in ADB/CDK In-Reply-To: References: <48200cee-2e78-510d-cf2d-b3b671064ada@redhat.com> Message-ID: <10db2693-ef5b-820d-04b1-beffe8b8be79@redhat.com> On 07/21/2016 05:22 PM, Karanbir Singh wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > On 21/07/16 12:25, Lalatendu Mohanty wrote: >> Hi, >> >> CentOS and RHEL is now providing docker-latest RPM along with >> regular docker package. Should we include it as part of ADB . IMO >> yes we should as it will give access to newer docker version to >> user if they need it. Also the question is what version of docker >> should be default installed in ADB? >> >> Let us know your thoughts. >> >> [1] >> http://mirror.centos.org/centos-7/7/extras/x86_64/Packages/docker-late > st-1.10.3-44.el7.centos.x86_64.rpm >> > What is the user engagement around ADB ? do we know who they are and > what they are doing with ADB ? We have not seen any user engagement around ADB. So we do not know about how users use the ADB. But we see steady downloads of ADB Vagrant box. Hopefully it is not an automated script doing the downloads. Thanks, Lala > > > > - -- > Karanbir Singh, Project Lead, The CentOS Project, London, UK > Red Hat Ext. 8274455 | DID: 0044 207 009 4455 > -----BEGIN PGP SIGNATURE----- > Version: GnuPG v2.0.22 (GNU/Linux) > > iQEcBAEBAgAGBQJXkLdmAAoJEI3Oi2Mx7xbtLxEIAKtjJm3kQvM3m9kSDZE7Ra2q > cHdorAAttEQFVlbkJaS7j0voauB4NNknJ2KhUlI08hQUYYval7Dtrv24lUwqNqEH > rDubrsXSDjbC3GKXdDV3HCuaZb+vsrazZ1ugQFxN42Q6zTb+ZnNKgAehmyFRXHzO > Nu0YpdxACuujCgvvDHJA1Q3QtQfoN58AbQBLMeTwXgubk8mCxTIfc24yTcQ/9aHh > 8fEC9H9Tafno7yBVkZLuTlqa3WwrPfRo/gn7RRhF3ZDGx6TgCbN1jOG4nUjt1nxL > 1ddYoWTsNZssP4hBexAWTbwkR2bbe4UGD+U26XIO/s704aTphdQV1h2BDFNMap8= > =Ri7N > -----END PGP SIGNATURE----- > > _______________________________________________ > Devtools mailing list > Devtools at redhat.com > https://www.redhat.com/mailman/listinfo/devtools From rstryker at redhat.com Mon Jul 25 18:12:42 2016 From: rstryker at redhat.com (Robert Stryker) Date: Mon, 25 Jul 2016 14:12:42 -0400 Subject: [Devtools] C/O CDK SMEs: Windows user going off the rails somewhere along the line In-Reply-To: References: Message-ID: The exception listed doesn't seem related to the color characters at all. Rather, it seems reminiscent of the service-manager call never completing. It seems we fetch all the output but we never get an exit status for the service-manager process we launched, and so we throw a timeout exception. Does anyone remember this issue cropping up before? Anyone remember a jira id for it? On Fri, Jul 22, 2016 at 8:37 AM, Todd Mancini wrote: > When you document it, please leave out the "and reboot" part, as that's a > very dramatic solution to a much easier problem. The user simply needs to > get the updated environment into their current context. I can help with the > wording/instructions relative to that. > > On Fri, Jul 22, 2016 at 8:27 AM, Rick Wagner wrote: > >> Many thanks, Jeff. >> >> We'll ask our customer to try this workaround. (We'll document it in KCS >> for later usage, also.) >> >> Rick >> >> On Fri, Jul 22, 2016 at 2:46 AM, Jean-Francois Maury >> wrote: >> >>> Rick, >>> >>> we have found an issue regarding the output of vagrant-registration >>> being corrupted by escape characters. We've fixed and it will be included >>> in this Sprint bits of DevStudio. >>> There is a possible workaround: define the env variable (on Windows >>> using the Control Panel) VAGRANT_NO_COLOR and set the value to 1. I would >>> suggest rebooting your machine and launch DevStudio again. >>> >>> Jeff >>> >>> On Thu, Jul 21, 2016 at 9:54 PM, Rick Wagner wrote: >>> >>>> Hello CDK SMEs, >>>> >>>> We have a support case where the user is unable to use the CDK. They >>>> have installed via Development Suite installer and offer the following: >>>> >>>> ------------------------------------------------- >>>> I installed the Suite and tried to start the server Container >>>> Development Environment and it seems it started successfully (i attached >>>> log on file vagrant_up.txt). But I received this error after server >>>> started: "Unable to configure docker and openshift. Calls to vagrant >>>> service-manager are returning empty environments." >>>> -------------------------------------------------- >>>> >>>> >>>> We've compared the vagrant log to a lab machine known to work, we see a >>>> difference starting with vagrant-registration's actions. (See screenshot >>>> below.) >>>> >>>> A comparison of the vagrant plug-ins shows the user has the same >>>> versions the lab box has. >>>> >>>> The Eclipse log offers us the following. Note especially the curious >>>> phrase "Calls to vagrant service-manager are returning empty environments.". >>>> >>>> ------------------------------------------------------ >>>> !ENTRY org.jboss.tools.openshift.cdk.server 4 0 2016-07-21 09:48:26.869 >>>> !MESSAGE Unable to successfully complete a call to vagrant >>>> service-manager. >>>> !STACK 0 >>>> java.util.concurrent.TimeoutException: Process output: >>>> ^[[0m # docker env:^[[0m # Set the following environment >>>> variables to enable access to the # docker daemon running inside of the >>>> vagrant virtual machine: export DOCKER_HOST=tcp://10.1.2.2:2376 >>>> export >>>> DOCKER_CERT_PATH='C:\Pedro\Software\Openshift_RHCDK_suite10\cdk\components\rhel\rhel-ose\.vagrant\machines\default\virtualbox\docker\' >>>> export DOCKER_TLS_VERIFY=1 export DOCKER_API_VERSION=1.21 ^[[0m^[[0m >>>> ^[[0m # openshift env:^[[0m ^[[0m# You can access the OpenShift console >>>> on: https://10.1.2.2:8443/console # To use OpenShift CLI, run: oc >>>> login https://10.1.2.2:8443 export OPENSHIFT_URL= >>>> https://10.1.2.2:8443 export OPENSHIFT_WEB_CONSOLE= >>>> https://10.1.2.2:8443/console export DOCKER_REGISTRY= >>>> hub.openshift.rhel-cdk.10.1.2.2.xip.io^[[0m ^[[0m # run following >>>> command to configure your shell: # eval "$(VAGRANT_NO_COLOR=1 vagrant >>>> service-manager env | tr -d '\r')"^[[0m >>>> at >>>> org.jboss.tools.openshift.cdk.server.core.internal.adapter.controllers.VagrantLaunchUtility.call(VagrantLaunchUtility.java:186) >>>> at >>>> org.jboss.tools.openshift.cdk.server.core.internal.adapter.controllers.VagrantLaunchUtility.call(VagrantLaunchUtility.java:153) >>>> at >>>> org.jboss.tools.openshift.cdk.server.core.internal.listeners.ServiceManagerEnvironment.loadServiceManagerEnvironment(ServiceManagerEnvironment.java:108) >>>> at >>>> org.jboss.tools.openshift.cdk.server.core.internal.listeners.ServiceManagerEnvironment.loadServiceManagerEnvironment(ServiceManagerEnvironment.java:85) >>>> at >>>> org.jboss.tools.openshift.cdk.server.core.internal.listeners.ServiceManagerEnvironment.getOrLoadServiceManagerEnvironment(ServiceManagerEnvironment.java:67) >>>> at >>>> org.jboss.tools.openshift.cdk.server.core.internal.listeners.ServiceManagerEnvironment.getOrLoadServiceManagerEnvironment(ServiceManagerEnvironment.java:59) >>>> at >>>> org.jboss.tools.openshift.cdk.server.core.internal.adapter.VagrantPoller.checkOpenShiftHealth(VagrantPoller.java:185) >>>> at >>>> org.jboss.tools.openshift.cdk.server.core.internal.adapter.VagrantPoller.onePing(VagrantPoller.java:174) >>>> at >>>> org.jboss.tools.openshift.cdk.server.core.internal.adapter.VagrantPoller.onePingSafe(VagrantPoller.java:154) >>>> at >>>> org.jboss.tools.openshift.cdk.server.core.internal.adapter.VagrantPoller.getCurrentStateSynchronous(VagrantPoller.java:133) >>>> at >>>> org.jboss.tools.openshift.cdk.server.core.internal.adapter.controllers.CDKLaunchController.handleProcessTerminated(CDKLaunchController.java:250) >>>> at >>>> org.jboss.tools.openshift.cdk.server.core.internal.adapter.controllers.CDKLaunchController.access$2(CDKLaunchController.java:242) >>>> at >>>> org.jboss.tools.openshift.cdk.server.core.internal.adapter.controllers.CDKLaunchController$2.run(CDKLaunchController.java:235) >>>> >>>> !ENTRY org.jboss.tools.openshift.cdk.server 4 0 2016-07-21 09:49:07.139 >>>> !MESSAGE Unable to successfully complete a call to vagrant >>>> service-manager. >>>> !STACK 0 >>>> java.util.concurrent.TimeoutException: Process output: >>>> ^[[0m # docker env:^[[0m # Set the following environment >>>> variables to enable access to the # docker daemon running inside of the >>>> vagrant virtual machine: export DOCKER_HOST=tcp://10.1.2.2:2376 >>>> export >>>> DOCKER_CERT_PATH='C:\Pedro\Software\Openshift_RHCDK_suite10\cdk\components\rhel\rhel-ose\.vagrant\machines\default\virtualbox\docker\' >>>> export DOCKER_TLS_VERIFY=1 export DOCKER_API_VERSION=1.21 ^[[0m^[[0m >>>> ^[[0m # openshift env:^[[0m ^[[0m# You can access the OpenShift console >>>> on: https://10.1.2.2:8443/console # To use OpenShift CLI, run: oc >>>> login https://10.1.2.2:8443 export OPENSHIFT_URL= >>>> https://10.1.2.2:8443 export OPENSHIFT_WEB_CONSOLE= >>>> https://10.1.2.2:8443/console export DOCKER_REGISTRY= >>>> hub.openshift.rhel-cdk.10.1.2.2.xip.io^[[0m ^[[0m # run following >>>> command to configure your shell: # eval "$(VAGRANT_NO_COLOR=1 vagrant >>>> service-manager env | tr -d '\r')"^[[0m >>>> at >>>> org.jboss.tools.openshift.cdk.server.core.internal.adapter.controllers.VagrantLaunchUtility.call(VagrantLaunchUtility.java:186) >>>> at >>>> org.jboss.tools.openshift.cdk.server.core.internal.adapter.controllers.VagrantLaunchUtility.call(VagrantLaunchUtility.java:153) >>>> at >>>> org.jboss.tools.openshift.cdk.server.core.internal.listeners.ServiceManagerEnvironment.loadServiceManagerEnvironment(ServiceManagerEnvironment.java:108) >>>> at >>>> org.jboss.tools.openshift.cdk.server.core.internal.listeners.ServiceManagerEnvironment.loadServiceManagerEnvironment(ServiceManagerEnvironment.java:85) >>>> at >>>> org.jboss.tools.openshift.cdk.server.core.internal.listeners.ServiceManagerEnvironment.getOrLoadServiceManagerEnvironment(ServiceManagerEnvironment.java:67) >>>> at >>>> org.jboss.tools.openshift.cdk.server.core.internal.listeners.ServiceManagerEnvironment.getOrLoadServiceManagerEnvironment(ServiceManagerEnvironment.java:59) >>>> at >>>> org.jboss.tools.openshift.cdk.server.core.internal.listeners.ConfigureDependentFrameworksListener.configureFrameworks(ConfigureDependentFrameworksListener.java:53) >>>> at >>>> org.jboss.tools.openshift.cdk.server.core.internal.listeners.ConfigureDependentFrameworksListener$1.run(ConfigureDependentFrameworksListener.java:43) >>>> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55) >>>> >>>> !ENTRY org.jboss.tools.openshift.cdk.server.core 4 0 2016-07-21 >>>> 09:49:07.142 >>>> !MESSAGE Unable to configure docker and openshift. Calls to vagrant >>>> service-manager are returning empty environments. >>>> >>>> >>>> -------------------------------------------------------------------------------------- >>>> >>>> >>>> >>>> >>>> Any suggestions are greatly appreciated. >>>> >>>> Thanks, >>>> >>>> Rick >>>> >>>> >>>> >>>> >>>> >>>> >>>> [image: Inline image 2] >>>> >>>> _______________________________________________ >>>> 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: -------------- next part -------------- A non-text attachment was scrubbed... Name: image.png Type: image/png Size: 246410 bytes Desc: not available URL: From cdrage at redhat.com Mon Jul 25 21:03:16 2016 From: cdrage at redhat.com (Charlie Drage) Date: Mon, 25 Jul 2016 17:03:16 -0400 Subject: [Devtools] Atomic App 0.6.2 release Message-ID: <20160725210316.GA1@e29ae4f6d913> Hey all! We're going to release Atomic App 0.6.2 this week on Wednesday. One of the biggest features is the `atomicapp index` command. If you have any open PR's which you'd like merged before the release, please ping the respective people! Many thanks, -- Charlie Drage Red Hat - Dev Tools / Project Atomic PGP - 4096R/C037D617 http://pgp.mit.edu/pks/lookup?op=get&search=0xDA227403C037D617 From alkazako at redhat.com Mon Jul 25 23:38:30 2016 From: alkazako at redhat.com (Alexey Kazakov) Date: Mon, 25 Jul 2016 16:38:30 -0700 Subject: [Devtools] C/O CDK SMEs: Windows user going off the rails somewhere along the line In-Reply-To: References: Message-ID: <5796A2F6.9000809@redhat.com> Rob, you mean this exception is caused by the issue similar to the issue we had with vagrant-sshfs: https://issues.jboss.org/browse/JBIDE-22604m ? And what is the JIRA for the bug with vagrant-registration being corrupted by escape characters mentioned by Jeff? On 07/25/2016 11:12 AM, Robert Stryker wrote: > The exception listed doesn't seem related to the color characters at > all. Rather, it seems reminiscent of the service-manager call never > completing. It seems we fetch all the output but we never get an exit > status for the service-manager process we launched, and so we throw a > timeout exception. > > Does anyone remember this issue cropping up before? Anyone remember a > jira id for it? > > On Fri, Jul 22, 2016 at 8:37 AM, Todd Mancini > wrote: > > When you document it, please leave out the "and reboot" part, as > that's a very dramatic solution to a much easier problem. The user > simply needs to get the updated environment into their current > context. I can help with the wording/instructions relative to that. > > On Fri, Jul 22, 2016 at 8:27 AM, Rick Wagner > wrote: > > Many thanks, Jeff. > > We'll ask our customer to try this workaround. (We'll > document it in KCS for later usage, also.) > > Rick > > On Fri, Jul 22, 2016 at 2:46 AM, Jean-Francois Maury > > wrote: > > Rick, > > we have found an issue regarding the output of > vagrant-registration being corrupted by escape characters. > We've fixed and it will be included in this Sprint bits of > DevStudio. > There is a possible workaround: define the env variable > (on Windows using the Control Panel) VAGRANT_NO_COLOR and > set the value to 1. I would suggest rebooting your machine > and launch DevStudio again. > > Jeff > > On Thu, Jul 21, 2016 at 9:54 PM, Rick Wagner > > wrote: > > Hello CDK SMEs, > > We have a support case where the user is unable to use > the CDK. They have installed via Development Suite > installer and offer the following: > > ------------------------------------------------- > I installed the Suite and tried to start the server > Container Development Environment and it seems it > started successfully (i attached log on file > vagrant_up.txt). But I received this error after > server started: "Unable to configure docker and > openshift. Calls to vagrant service-manager are > returning empty environments." > -------------------------------------------------- > > > We've compared the vagrant log to a lab machine known > to work, we see a difference starting with > vagrant-registration's actions. (See screenshot below.) > > A comparison of the vagrant plug-ins shows the user > has the same versions the lab box has. > > The Eclipse log offers us the following. Note > especially the curious phrase "Calls to vagrant > service-manager are returning empty environments.". > > ------------------------------------------------------ > !ENTRY org.jboss.tools.openshift.cdk.server 4 0 > 2016-07-21 09:48:26.869 > !MESSAGE Unable to successfully complete a call to > vagrant service-manager. > !STACK 0 > java.util.concurrent.TimeoutException: Process output: > ^[[0m # docker env:^[[0m # Set the following > environment variables to enable access to the # > docker daemon running inside of the vagrant virtual > machine: export DOCKER_HOST=tcp://10.1.2.2:2376 > export > DOCKER_CERT_PATH='C:\Pedro\Software\Openshift_RHCDK_suite10\cdk\components\rhel\rhel-ose\.vagrant\machines\default\virtualbox\docker\' > export DOCKER_TLS_VERIFY=1 export > DOCKER_API_VERSION=1.21 ^[[0m^[[0m ^[[0m # > openshift env:^[[0m ^[[0m# You can access the > OpenShift console on: https://10.1.2.2:8443/console # > To use OpenShift CLI, run: oc login > https://10.1.2.2:8443 export > OPENSHIFT_URL=https://10.1.2.2:8443 export > OPENSHIFT_WEB_CONSOLE=https://10.1.2.2:8443/console > export > DOCKER_REGISTRY=hub.openshift.rhel-cdk.10.1.2.2.xip.io > ^[[0m > ^[[0m # run following command to configure your > shell: # eval "$(VAGRANT_NO_COLOR=1 vagrant > service-manager env | tr -d '\r')"^[[0m > at > org.jboss.tools.openshift.cdk.server.core.internal.adapter.controllers.VagrantLaunchUtility.call(VagrantLaunchUtility.java:186) > at > org.jboss.tools.openshift.cdk.server.core.internal.adapter.controllers.VagrantLaunchUtility.call(VagrantLaunchUtility.java:153) > at > org.jboss.tools.openshift.cdk.server.core.internal.listeners.ServiceManagerEnvironment.loadServiceManagerEnvironment(ServiceManagerEnvironment.java:108) > at > org.jboss.tools.openshift.cdk.server.core.internal.listeners.ServiceManagerEnvironment.loadServiceManagerEnvironment(ServiceManagerEnvironment.java:85) > at > org.jboss.tools.openshift.cdk.server.core.internal.listeners.ServiceManagerEnvironment.getOrLoadServiceManagerEnvironment(ServiceManagerEnvironment.java:67) > at > org.jboss.tools.openshift.cdk.server.core.internal.listeners.ServiceManagerEnvironment.getOrLoadServiceManagerEnvironment(ServiceManagerEnvironment.java:59) > at > org.jboss.tools.openshift.cdk.server.core.internal.adapter.VagrantPoller.checkOpenShiftHealth(VagrantPoller.java:185) > at > org.jboss.tools.openshift.cdk.server.core.internal.adapter.VagrantPoller.onePing(VagrantPoller.java:174) > at > org.jboss.tools.openshift.cdk.server.core.internal.adapter.VagrantPoller.onePingSafe(VagrantPoller.java:154) > at > org.jboss.tools.openshift.cdk.server.core.internal.adapter.VagrantPoller.getCurrentStateSynchronous(VagrantPoller.java:133) > at > org.jboss.tools.openshift.cdk.server.core.internal.adapter.controllers.CDKLaunchController.handleProcessTerminated(CDKLaunchController.java:250) > at > org.jboss.tools.openshift.cdk.server.core.internal.adapter.controllers.CDKLaunchController.access$2(CDKLaunchController.java:242) > at > org.jboss.tools.openshift.cdk.server.core.internal.adapter.controllers.CDKLaunchController$2.run(CDKLaunchController.java:235) > > !ENTRY org.jboss.tools.openshift.cdk.server 4 0 > 2016-07-21 09:49:07.139 > !MESSAGE Unable to successfully complete a call to > vagrant service-manager. > !STACK 0 > java.util.concurrent.TimeoutException: Process output: > ^[[0m # docker env:^[[0m # Set the following > environment variables to enable access to the # > docker daemon running inside of the vagrant virtual > machine: export DOCKER_HOST=tcp://10.1.2.2:2376 > export > DOCKER_CERT_PATH='C:\Pedro\Software\Openshift_RHCDK_suite10\cdk\components\rhel\rhel-ose\.vagrant\machines\default\virtualbox\docker\' > export DOCKER_TLS_VERIFY=1 export > DOCKER_API_VERSION=1.21 ^[[0m^[[0m ^[[0m # > openshift env:^[[0m ^[[0m# You can access the > OpenShift console on: https://10.1.2.2:8443/console # > To use OpenShift CLI, run: oc login > https://10.1.2.2:8443 export > OPENSHIFT_URL=https://10.1.2.2:8443 export > OPENSHIFT_WEB_CONSOLE=https://10.1.2.2:8443/console > export > DOCKER_REGISTRY=hub.openshift.rhel-cdk.10.1.2.2.xip.io > ^[[0m > ^[[0m # run following command to configure your > shell: # eval "$(VAGRANT_NO_COLOR=1 vagrant > service-manager env | tr -d '\r')"^[[0m > at > org.jboss.tools.openshift.cdk.server.core.internal.adapter.controllers.VagrantLaunchUtility.call(VagrantLaunchUtility.java:186) > at > org.jboss.tools.openshift.cdk.server.core.internal.adapter.controllers.VagrantLaunchUtility.call(VagrantLaunchUtility.java:153) > at > org.jboss.tools.openshift.cdk.server.core.internal.listeners.ServiceManagerEnvironment.loadServiceManagerEnvironment(ServiceManagerEnvironment.java:108) > at > org.jboss.tools.openshift.cdk.server.core.internal.listeners.ServiceManagerEnvironment.loadServiceManagerEnvironment(ServiceManagerEnvironment.java:85) > at > org.jboss.tools.openshift.cdk.server.core.internal.listeners.ServiceManagerEnvironment.getOrLoadServiceManagerEnvironment(ServiceManagerEnvironment.java:67) > at > org.jboss.tools.openshift.cdk.server.core.internal.listeners.ServiceManagerEnvironment.getOrLoadServiceManagerEnvironment(ServiceManagerEnvironment.java:59) > at > org.jboss.tools.openshift.cdk.server.core.internal.listeners.ConfigureDependentFrameworksListener.configureFrameworks(ConfigureDependentFrameworksListener.java:53) > at > org.jboss.tools.openshift.cdk.server.core.internal.listeners.ConfigureDependentFrameworksListener$1.run(ConfigureDependentFrameworksListener.java:43) > at > org.eclipse.core.internal.jobs.Worker.run(Worker.java:55) > > !ENTRY org.jboss.tools.openshift.cdk.server.core 4 0 > 2016-07-21 09:49:07.142 > !MESSAGE Unable to configure docker and openshift. > Calls to vagrant service-manager are returning empty > environments. > > -------------------------------------------------------------------------------------- > > > > > Any suggestions are greatly appreciated. > > Thanks, > > Rick > > > > > > > Inline image 2 > > _______________________________________________ > 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: -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: image/png Size: 246410 bytes Desc: not available URL: From rstryker at redhat.com Tue Jul 26 04:32:15 2016 From: rstryker at redhat.com (Robert Stryker) Date: Tue, 26 Jul 2016 00:32:15 -0400 Subject: [Devtools] C/O CDK SMEs: Windows user going off the rails somewhere along the line In-Reply-To: <5796A2F6.9000809@redhat.com> References: <5796A2F6.9000809@redhat.com> Message-ID: Well, just by looking at the trace included in this thread, it's obvious we're running vagrant service-manager, and we're getting output, but then we're getting a timeout. I can only conclude that somehow the process isn't terminating. I could probably clean up my error handling a bit to *try* to recover from this, ie, in the event of a timeout, see if we have any response text at all, and see what we can do about it. But I'm not even sure that would be the correct solution. I believe Jeff Murray was referencing https://issues.jboss.org/browse/JBIDE-22664 but this issue isn't about the registration but rather during vagrant service-manager calls. So it'd be the same location in the code (or similar / nearby at least). But the fact that it's a timeout exception rather than a parse exception means the error isn't caused by the color codes. It's caused by the call to vagrant service-manager not completing in a timely fashion. On Mon, Jul 25, 2016 at 7:38 PM, Alexey Kazakov wrote: > Rob, you mean this exception is caused by the issue similar to the issue > we had with vagrant-sshfs: https://issues.jboss.org/browse/JBIDE-22604m ? > > And what is the JIRA for the bug with vagrant-registration being corrupted > by escape characters mentioned by Jeff? > > > On 07/25/2016 11:12 AM, Robert Stryker wrote: > > The exception listed doesn't seem related to the color characters at all. > Rather, it seems reminiscent of the service-manager call never completing. > It seems we fetch all the output but we never get an exit status for the > service-manager process we launched, and so we throw a timeout exception. > > Does anyone remember this issue cropping up before? Anyone remember a > jira id for it? > > On Fri, Jul 22, 2016 at 8:37 AM, Todd Mancini wrote: > >> When you document it, please leave out the "and reboot" part, as that's a >> very dramatic solution to a much easier problem. The user simply needs to >> get the updated environment into their current context. I can help with the >> wording/instructions relative to that. >> >> On Fri, Jul 22, 2016 at 8:27 AM, Rick Wagner < >> rwagner at redhat.com> wrote: >> >>> Many thanks, Jeff. >>> >>> We'll ask our customer to try this workaround. (We'll document it in >>> KCS for later usage, also.) >>> >>> Rick >>> >>> On Fri, Jul 22, 2016 at 2:46 AM, Jean-Francois Maury >>> wrote: >>> >>>> Rick, >>>> >>>> we have found an issue regarding the output of vagrant-registration >>>> being corrupted by escape characters. We've fixed and it will be included >>>> in this Sprint bits of DevStudio. >>>> There is a possible workaround: define the env variable (on Windows >>>> using the Control Panel) VAGRANT_NO_COLOR and set the value to 1. I would >>>> suggest rebooting your machine and launch DevStudio again. >>>> >>>> Jeff >>>> >>>> On Thu, Jul 21, 2016 at 9:54 PM, Rick Wagner < >>>> rwagner at redhat.com> wrote: >>>> >>>>> Hello CDK SMEs, >>>>> >>>>> We have a support case where the user is unable to use the CDK. They >>>>> have installed via Development Suite installer and offer the following: >>>>> >>>>> ------------------------------------------------- >>>>> I installed the Suite and tried to start the server Container >>>>> Development Environment and it seems it started successfully (i attached >>>>> log on file vagrant_up.txt). But I received this error after server >>>>> started: "Unable to configure docker and openshift. Calls to vagrant >>>>> service-manager are returning empty environments." >>>>> -------------------------------------------------- >>>>> >>>>> >>>>> We've compared the vagrant log to a lab machine known to work, we see >>>>> a difference starting with vagrant-registration's actions. (See screenshot >>>>> below.) >>>>> >>>>> A comparison of the vagrant plug-ins shows the user has the same >>>>> versions the lab box has. >>>>> >>>>> The Eclipse log offers us the following. Note especially the curious >>>>> phrase "Calls to vagrant service-manager are returning empty environments.". >>>>> >>>>> ------------------------------------------------------ >>>>> !ENTRY org.jboss.tools.openshift.cdk.server 4 0 2016-07-21 09:48:26.869 >>>>> !MESSAGE Unable to successfully complete a call to vagrant >>>>> service-manager. >>>>> !STACK 0 >>>>> java.util.concurrent.TimeoutException: Process output: >>>>> ^[[0m # docker env:^[[0m # Set the following environment >>>>> variables to enable access to the # docker daemon running inside of the >>>>> vagrant virtual machine: export DOCKER_HOST=tcp://10.1.2.2:2376 >>>>> export >>>>> DOCKER_CERT_PATH='C:\Pedro\Software\Openshift_RHCDK_suite10\cdk\components\rhel\rhel-ose\.vagrant\machines\default\virtualbox\docker\' >>>>> export DOCKER_TLS_VERIFY=1 export DOCKER_API_VERSION=1.21 ^[[0m^[[0m >>>>> ^[[0m # openshift env:^[[0m ^[[0m# You can access the OpenShift console >>>>> on: https://10.1.2.2:8443/console # >>>>> To use OpenShift CLI, run: oc login >>>>> https://10.1.2.2:8443 export OPENSHIFT_URL= >>>>> https://10.1.2.2:8443 export OPENSHIFT_WEB_CONSOLE= >>>>> https://10.1.2.2:8443/console export >>>>> DOCKER_REGISTRY=hub.openshift.rhel-cdk.10.1.2.2.xip.io^[[0m ^[[0m >>>>> # run following command to configure your shell: # eval >>>>> "$(VAGRANT_NO_COLOR=1 vagrant service-manager env | tr -d '\r')"^[[0m >>>>> at >>>>> org.jboss.tools.openshift.cdk.server.core.internal.adapter.controllers.VagrantLaunchUtility.call(VagrantLaunchUtility.java:186) >>>>> at >>>>> org.jboss.tools.openshift.cdk.server.core.internal.adapter.controllers.VagrantLaunchUtility.call(VagrantLaunchUtility.java:153) >>>>> at >>>>> org.jboss.tools.openshift.cdk.server.core.internal.listeners.ServiceManagerEnvironment.loadServiceManagerEnvironment(ServiceManagerEnvironment.java:108) >>>>> at >>>>> org.jboss.tools.openshift.cdk.server.core.internal.listeners.ServiceManagerEnvironment.loadServiceManagerEnvironment(ServiceManagerEnvironment.java:85) >>>>> at >>>>> org.jboss.tools.openshift.cdk.server.core.internal.listeners.ServiceManagerEnvironment.getOrLoadServiceManagerEnvironment(ServiceManagerEnvironment.java:67) >>>>> at >>>>> org.jboss.tools.openshift.cdk.server.core.internal.listeners.ServiceManagerEnvironment.getOrLoadServiceManagerEnvironment(ServiceManagerEnvironment.java:59) >>>>> at >>>>> org.jboss.tools.openshift.cdk.server.core.internal.adapter.VagrantPoller.checkOpenShiftHealth(VagrantPoller.java:185) >>>>> at >>>>> org.jboss.tools.openshift.cdk.server.core.internal.adapter.VagrantPoller.onePing(VagrantPoller.java:174) >>>>> at >>>>> org.jboss.tools.openshift.cdk.server.core.internal.adapter.VagrantPoller.onePingSafe(VagrantPoller.java:154) >>>>> at >>>>> org.jboss.tools.openshift.cdk.server.core.internal.adapter.VagrantPoller.getCurrentStateSynchronous(VagrantPoller.java:133) >>>>> at >>>>> org.jboss.tools.openshift.cdk.server.core.internal.adapter.controllers.CDKLaunchController.handleProcessTerminated(CDKLaunchController.java:250) >>>>> at >>>>> org.jboss.tools.openshift.cdk.server.core.internal.adapter.controllers.CDKLaunchController.access$2(CDKLaunchController.java:242) >>>>> at >>>>> org.jboss.tools.openshift.cdk.server.core.internal.adapter.controllers.CDKLaunchController$2.run(CDKLaunchController.java:235) >>>>> >>>>> !ENTRY org.jboss.tools.openshift.cdk.server 4 0 2016-07-21 09:49:07.139 >>>>> !MESSAGE Unable to successfully complete a call to vagrant >>>>> service-manager. >>>>> !STACK 0 >>>>> java.util.concurrent.TimeoutException: Process output: >>>>> ^[[0m # docker env:^[[0m # Set the following environment >>>>> variables to enable access to the # docker daemon running inside of the >>>>> vagrant virtual machine: export DOCKER_HOST=tcp://10.1.2.2:2376 >>>>> export >>>>> DOCKER_CERT_PATH='C:\Pedro\Software\Openshift_RHCDK_suite10\cdk\components\rhel\rhel-ose\.vagrant\machines\default\virtualbox\docker\' >>>>> export DOCKER_TLS_VERIFY=1 export DOCKER_API_VERSION=1.21 ^[[0m^[[0m >>>>> ^[[0m # openshift env:^[[0m ^[[0m# You can access the OpenShift console >>>>> on: https://10.1.2.2:8443/console # >>>>> To use OpenShift CLI, run: oc login >>>>> https://10.1.2.2:8443 export OPENSHIFT_URL= >>>>> https://10.1.2.2:8443 export OPENSHIFT_WEB_CONSOLE= >>>>> https://10.1.2.2:8443/console export >>>>> DOCKER_REGISTRY=hub.openshift.rhel-cdk.10.1.2.2.xip.io^[[0m ^[[0m >>>>> # run following command to configure your shell: # eval >>>>> "$(VAGRANT_NO_COLOR=1 vagrant service-manager env | tr -d '\r')"^[[0m >>>>> at >>>>> org.jboss.tools.openshift.cdk.server.core.internal.adapter.controllers.VagrantLaunchUtility.call(VagrantLaunchUtility.java:186) >>>>> at >>>>> org.jboss.tools.openshift.cdk.server.core.internal.adapter.controllers.VagrantLaunchUtility.call(VagrantLaunchUtility.java:153) >>>>> at >>>>> org.jboss.tools.openshift.cdk.server.core.internal.listeners.ServiceManagerEnvironment.loadServiceManagerEnvironment(ServiceManagerEnvironment.java:108) >>>>> at >>>>> org.jboss.tools.openshift.cdk.server.core.internal.listeners.ServiceManagerEnvironment.loadServiceManagerEnvironment(ServiceManagerEnvironment.java:85) >>>>> at >>>>> org.jboss.tools.openshift.cdk.server.core.internal.listeners.ServiceManagerEnvironment.getOrLoadServiceManagerEnvironment(ServiceManagerEnvironment.java:67) >>>>> at >>>>> org.jboss.tools.openshift.cdk.server.core.internal.listeners.ServiceManagerEnvironment.getOrLoadServiceManagerEnvironment(ServiceManagerEnvironment.java:59) >>>>> at >>>>> org.jboss.tools.openshift.cdk.server.core.internal.listeners.ConfigureDependentFrameworksListener.configureFrameworks(ConfigureDependentFrameworksListener.java:53) >>>>> at >>>>> org.jboss.tools.openshift.cdk.server.core.internal.listeners.ConfigureDependentFrameworksListener$1.run(ConfigureDependentFrameworksListener.java:43) >>>>> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55) >>>>> >>>>> !ENTRY org.jboss.tools.openshift.cdk.server.core 4 0 2016-07-21 >>>>> 09:49:07.142 >>>>> !MESSAGE Unable to configure docker and openshift. Calls to vagrant >>>>> service-manager are returning empty environments. >>>>> >>>>> >>>>> -------------------------------------------------------------------------------------- >>>>> >>>>> >>>>> >>>>> >>>>> Any suggestions are greatly appreciated. >>>>> >>>>> Thanks, >>>>> >>>>> Rick >>>>> >>>>> >>>>> >>>>> >>>>> >>>>> >>>>> [image: Inline image 2] >>>>> >>>>> _______________________________________________ >>>>> 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 listDevtools at redhat.comhttps://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: -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: image/png Size: 246410 bytes Desc: not available URL: From jmaury at redhat.com Tue Jul 26 07:26:23 2016 From: jmaury at redhat.com (Jean-Francois Maury) Date: Tue, 26 Jul 2016 09:26:23 +0200 Subject: [Devtools] C/O CDK SMEs: Windows user going off the rails somewhere along the line In-Reply-To: References: <5796A2F6.9000809@redhat.com> Message-ID: Yes the jira is the correct one If this is related to service registration this is fixed by version 1.0.1 I think Jeff Le 26 juil. 2016 06:32, "Robert Stryker" a ?crit : Well, just by looking at the trace included in this thread, it's obvious we're running vagrant service-manager, and we're getting output, but then we're getting a timeout. I can only conclude that somehow the process isn't terminating. I could probably clean up my error handling a bit to *try* to recover from this, ie, in the event of a timeout, see if we have any response text at all, and see what we can do about it. But I'm not even sure that would be the correct solution. I believe Jeff Murray was referencing https://issues.jboss.org/browse/JBIDE-22664 but this issue isn't about the registration but rather during vagrant service-manager calls. So it'd be the same location in the code (or similar / nearby at least). But the fact that it's a timeout exception rather than a parse exception means the error isn't caused by the color codes. It's caused by the call to vagrant service-manager not completing in a timely fashion. On Mon, Jul 25, 2016 at 7:38 PM, Alexey Kazakov wrote: > Rob, you mean this exception is caused by the issue similar to the issue > we had with vagrant-sshfs: https://issues.jboss.org/browse/JBIDE-22604m ? > > And what is the JIRA for the bug with vagrant-registration being corrupted > by escape characters mentioned by Jeff? > > > On 07/25/2016 11:12 AM, Robert Stryker wrote: > > The exception listed doesn't seem related to the color characters at all. > Rather, it seems reminiscent of the service-manager call never completing. > It seems we fetch all the output but we never get an exit status for the > service-manager process we launched, and so we throw a timeout exception. > > Does anyone remember this issue cropping up before? Anyone remember a > jira id for it? > > On Fri, Jul 22, 2016 at 8:37 AM, Todd Mancini wrote: > >> When you document it, please leave out the "and reboot" part, as that's a >> very dramatic solution to a much easier problem. The user simply needs to >> get the updated environment into their current context. I can help with the >> wording/instructions relative to that. >> >> On Fri, Jul 22, 2016 at 8:27 AM, Rick Wagner < >> rwagner at redhat.com> wrote: >> >>> Many thanks, Jeff. >>> >>> We'll ask our customer to try this workaround. (We'll document it in >>> KCS for later usage, also.) >>> >>> Rick >>> >>> On Fri, Jul 22, 2016 at 2:46 AM, Jean-Francois Maury >>> wrote: >>> >>>> Rick, >>>> >>>> we have found an issue regarding the output of vagrant-registration >>>> being corrupted by escape characters. We've fixed and it will be included >>>> in this Sprint bits of DevStudio. >>>> There is a possible workaround: define the env variable (on Windows >>>> using the Control Panel) VAGRANT_NO_COLOR and set the value to 1. I would >>>> suggest rebooting your machine and launch DevStudio again. >>>> >>>> Jeff >>>> >>>> On Thu, Jul 21, 2016 at 9:54 PM, Rick Wagner < >>>> rwagner at redhat.com> wrote: >>>> >>>>> Hello CDK SMEs, >>>>> >>>>> We have a support case where the user is unable to use the CDK. They >>>>> have installed via Development Suite installer and offer the following: >>>>> >>>>> ------------------------------------------------- >>>>> I installed the Suite and tried to start the server Container >>>>> Development Environment and it seems it started successfully (i attached >>>>> log on file vagrant_up.txt). But I received this error after server >>>>> started: "Unable to configure docker and openshift. Calls to vagrant >>>>> service-manager are returning empty environments." >>>>> -------------------------------------------------- >>>>> >>>>> >>>>> We've compared the vagrant log to a lab machine known to work, we see >>>>> a difference starting with vagrant-registration's actions. (See screenshot >>>>> below.) >>>>> >>>>> A comparison of the vagrant plug-ins shows the user has the same >>>>> versions the lab box has. >>>>> >>>>> The Eclipse log offers us the following. Note especially the curious >>>>> phrase "Calls to vagrant service-manager are returning empty environments.". >>>>> >>>>> ------------------------------------------------------ >>>>> !ENTRY org.jboss.tools.openshift.cdk.server 4 0 2016-07-21 09:48:26.869 >>>>> !MESSAGE Unable to successfully complete a call to vagrant >>>>> service-manager. >>>>> !STACK 0 >>>>> java.util.concurrent.TimeoutException: Process output: >>>>> ^[[0m # docker env:^[[0m # Set the following environment >>>>> variables to enable access to the # docker daemon running inside of the >>>>> vagrant virtual machine: export DOCKER_HOST=tcp://10.1.2.2:2376 >>>>> export >>>>> DOCKER_CERT_PATH='C:\Pedro\Software\Openshift_RHCDK_suite10\cdk\components\rhel\rhel-ose\.vagrant\machines\default\virtualbox\docker\' >>>>> export DOCKER_TLS_VERIFY=1 export DOCKER_API_VERSION=1.21 ^[[0m^[[0m >>>>> ^[[0m # openshift env:^[[0m ^[[0m# You can access the OpenShift console >>>>> on: https://10.1.2.2:8443/console # >>>>> To use OpenShift CLI, run: oc login >>>>> https://10.1.2.2:8443 export OPENSHIFT_URL= >>>>> https://10.1.2.2:8443 export OPENSHIFT_WEB_CONSOLE= >>>>> https://10.1.2.2:8443/console export >>>>> DOCKER_REGISTRY=hub.openshift.rhel-cdk.10.1.2.2.xip.io^[[0m ^[[0m >>>>> # run following command to configure your shell: # eval >>>>> "$(VAGRANT_NO_COLOR=1 vagrant service-manager env | tr -d '\r')"^[[0m >>>>> at >>>>> org.jboss.tools.openshift.cdk.server.core.internal.adapter.controllers.VagrantLaunchUtility.call(VagrantLaunchUtility.java:186) >>>>> at >>>>> org.jboss.tools.openshift.cdk.server.core.internal.adapter.controllers.VagrantLaunchUtility.call(VagrantLaunchUtility.java:153) >>>>> at >>>>> org.jboss.tools.openshift.cdk.server.core.internal.listeners.ServiceManagerEnvironment.loadServiceManagerEnvironment(ServiceManagerEnvironment.java:108) >>>>> at >>>>> org.jboss.tools.openshift.cdk.server.core.internal.listeners.ServiceManagerEnvironment.loadServiceManagerEnvironment(ServiceManagerEnvironment.java:85) >>>>> at >>>>> org.jboss.tools.openshift.cdk.server.core.internal.listeners.ServiceManagerEnvironment.getOrLoadServiceManagerEnvironment(ServiceManagerEnvironment.java:67) >>>>> at >>>>> org.jboss.tools.openshift.cdk.server.core.internal.listeners.ServiceManagerEnvironment.getOrLoadServiceManagerEnvironment(ServiceManagerEnvironment.java:59) >>>>> at >>>>> org.jboss.tools.openshift.cdk.server.core.internal.adapter.VagrantPoller.checkOpenShiftHealth(VagrantPoller.java:185) >>>>> at >>>>> org.jboss.tools.openshift.cdk.server.core.internal.adapter.VagrantPoller.onePing(VagrantPoller.java:174) >>>>> at >>>>> org.jboss.tools.openshift.cdk.server.core.internal.adapter.VagrantPoller.onePingSafe(VagrantPoller.java:154) >>>>> at >>>>> org.jboss.tools.openshift.cdk.server.core.internal.adapter.VagrantPoller.getCurrentStateSynchronous(VagrantPoller.java:133) >>>>> at >>>>> org.jboss.tools.openshift.cdk.server.core.internal.adapter.controllers.CDKLaunchController.handleProcessTerminated(CDKLaunchController.java:250) >>>>> at >>>>> org.jboss.tools.openshift.cdk.server.core.internal.adapter.controllers.CDKLaunchController.access$2(CDKLaunchController.java:242) >>>>> at >>>>> org.jboss.tools.openshift.cdk.server.core.internal.adapter.controllers.CDKLaunchController$2.run(CDKLaunchController.java:235) >>>>> >>>>> !ENTRY org.jboss.tools.openshift.cdk.server 4 0 2016-07-21 09:49:07.139 >>>>> !MESSAGE Unable to successfully complete a call to vagrant >>>>> service-manager. >>>>> !STACK 0 >>>>> java.util.concurrent.TimeoutException: Process output: >>>>> ^[[0m # docker env:^[[0m # Set the following environment >>>>> variables to enable access to the # docker daemon running inside of the >>>>> vagrant virtual machine: export DOCKER_HOST=tcp://10.1.2.2:2376 >>>>> export >>>>> DOCKER_CERT_PATH='C:\Pedro\Software\Openshift_RHCDK_suite10\cdk\components\rhel\rhel-ose\.vagrant\machines\default\virtualbox\docker\' >>>>> export DOCKER_TLS_VERIFY=1 export DOCKER_API_VERSION=1.21 ^[[0m^[[0m >>>>> ^[[0m # openshift env:^[[0m ^[[0m# You can access the OpenShift console >>>>> on: https://10.1.2.2:8443/console # >>>>> To use OpenShift CLI, run: oc login >>>>> https://10.1.2.2:8443 export OPENSHIFT_URL= >>>>> https://10.1.2.2:8443 export OPENSHIFT_WEB_CONSOLE= >>>>> https://10.1.2.2:8443/console export >>>>> DOCKER_REGISTRY=hub.openshift.rhel-cdk.10.1.2.2.xip.io^[[0m ^[[0m >>>>> # run following command to configure your shell: # eval >>>>> "$(VAGRANT_NO_COLOR=1 vagrant service-manager env | tr -d '\r')"^[[0m >>>>> at >>>>> org.jboss.tools.openshift.cdk.server.core.internal.adapter.controllers.VagrantLaunchUtility.call(VagrantLaunchUtility.java:186) >>>>> at >>>>> org.jboss.tools.openshift.cdk.server.core.internal.adapter.controllers.VagrantLaunchUtility.call(VagrantLaunchUtility.java:153) >>>>> at >>>>> org.jboss.tools.openshift.cdk.server.core.internal.listeners.ServiceManagerEnvironment.loadServiceManagerEnvironment(ServiceManagerEnvironment.java:108) >>>>> at >>>>> org.jboss.tools.openshift.cdk.server.core.internal.listeners.ServiceManagerEnvironment.loadServiceManagerEnvironment(ServiceManagerEnvironment.java:85) >>>>> at >>>>> org.jboss.tools.openshift.cdk.server.core.internal.listeners.ServiceManagerEnvironment.getOrLoadServiceManagerEnvironment(ServiceManagerEnvironment.java:67) >>>>> at >>>>> org.jboss.tools.openshift.cdk.server.core.internal.listeners.ServiceManagerEnvironment.getOrLoadServiceManagerEnvironment(ServiceManagerEnvironment.java:59) >>>>> at >>>>> org.jboss.tools.openshift.cdk.server.core.internal.listeners.ConfigureDependentFrameworksListener.configureFrameworks(ConfigureDependentFrameworksListener.java:53) >>>>> at >>>>> org.jboss.tools.openshift.cdk.server.core.internal.listeners.ConfigureDependentFrameworksListener$1.run(ConfigureDependentFrameworksListener.java:43) >>>>> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55) >>>>> >>>>> !ENTRY org.jboss.tools.openshift.cdk.server.core 4 0 2016-07-21 >>>>> 09:49:07.142 >>>>> !MESSAGE Unable to configure docker and openshift. Calls to vagrant >>>>> service-manager are returning empty environments. >>>>> >>>>> >>>>> -------------------------------------------------------------------------------------- >>>>> >>>>> >>>>> >>>>> >>>>> Any suggestions are greatly appreciated. >>>>> >>>>> Thanks, >>>>> >>>>> Rick >>>>> >>>>> >>>>> >>>>> >>>>> >>>>> >>>>> [image: Inline image 2] >>>>> >>>>> _______________________________________________ >>>>> 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 listDevtools at redhat.comhttps://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: -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: image/png Size: 246410 bytes Desc: not available URL: From degolovi at redhat.com Wed Jul 27 05:24:39 2016 From: degolovi at redhat.com (Denis Golovin) Date: Wed, 27 Jul 2016 01:24:39 -0400 (EDT) Subject: [Devtools] Development suite installer questions In-Reply-To: References: <1398019809.5131103.1468300175128.JavaMail.zimbra@redhat.com> Message-ID: <34572291.8597672.1469597079861.JavaMail.zimbra@redhat.com> Rick, Do you have any update on this case? Was customer able to solve the problem? I've opened issue for not setting proper user agent for http requests in DevSuite installer (see https://issues.jboss.org/browse/JBDS-3979). Thanks, Denis ----- Original Message ----- > From: "Rick Wagner" > To: "Denis Golovin" > Cc: devtools at redhat.com > Sent: Tuesday, July 12, 2016 6:09:20 AM > Subject: Re: [Devtools] Development suite installer questions > > Thanks much for that advice, Denis. > > We'll work with the customer to see if this can be used with the browser > 'whitelist' to enable use of the Development Suite. > > Rick > > On Tue, Jul 12, 2016 at 12:09 AM, Denis Golovin wrote: > > > Rick, > > > > see my comments inline > > > > ----- Original Message ----- > > > From: "Rick Wagner" > > > To: devtools at redhat.com > > > Sent: Monday, July 11, 2016 7:20:02 AM > > > Subject: [Devtools] Development suite installer questions > > > > > > Hello DevTools, > > > > > > We're working with a customer that brings a few interesting questions > > about > > > the installer. > > > > > > > > > Question 1: > > > > > > When an attempt is made to download the Development Suite, we see the > > error: > > > > > > "Oops. Something went wrong > > > The download failed. Please check if you have internet access, connected > > to > > > VPN, have correct configuration for proxy server. Try to download again > > > after problem is fixed." > > > > > > The user tells us they are behind a proxy server. Do we have any specific > > > recommendations for a remedy? > > > > I see first problem here is that message doesn't say what exactly went > > wrong and what installer was trying to download. > > > > It could be proxy issue related to: > > 1. User-Agent header does not set it at all; > > 2. Download for Vagrant and Oracle Virtualbox uses redirects on > > developers.redhat.com not direct links see > > details here https://issues.jboss.org/browse/ORG-2929. > > > > Could you ask if links > > > > http://developers.stage.redhat.com/redirect/to/virtualbox-5.0.8.download > > http://developers.stage.redhat.com/redirect/to/vagrant-1.7.4.download > > > > work from browser? > > > > > > > > > > > Question 2: > > > > > > The same user notes that when they do get the installer, it urges them to > > > install Cygwin even though it's already present. Is there a way to avoid > > > this? > > > > Cygwin detection is not implemented yet and it might become optional > > component to install soon, see supported terminals discussion. > > > > Thanks, > > Denis > > > > > > > > Thanks, > > > > > > Rick > > > > > > > > > _______________________________________________ > > > Devtools mailing list > > > Devtools at redhat.com > > > https://www.redhat.com/mailman/listinfo/devtools > > > > > > From mlabuda at redhat.com Wed Jul 27 08:34:16 2016 From: mlabuda at redhat.com (Marian Labuda) Date: Wed, 27 Jul 2016 10:34:16 +0200 Subject: [Devtools] Fwd: [openshift-sme] Blog post on Debugging Java Application with the CDK In-Reply-To: References: Message-ID: I was able to find only section in "What's new" post http://tools.jboss.org/documentation/whatsnew/jbosstools/4.3.1.Final.html#openshift and there is a screencast from sprint demo call https://drive.google.com/a/redhat.com/file/d/0B8jMRJvPAz5EaXY3UnA1LWJnMlU/view (thanks to Jean-Francois Maury, and it starts around 6. minute). Marian On Tue, Jul 26, 2016 at 1:35 AM, Andrew Block wrote: > Thanks for the reviewing the post. Additional comments inline > > - Andy > > > Andrew Block > Red Hat Consulting > 101 N. Wacker, Suite 150 > Chicago, IL 60606 > andrew.block at redhat.com | m. (716) 870-2408 > > On July 25, 2016 at 5:20:21 AM, Marian Labuda (mlabuda at redhat.com) wrote: > > Nice, > > Just 2 notes (I did not read it whole, just a quick overview). I've > spotted in section "Using Red Hat JBoss Developer Studio to Connect to > OpenShift" that right double quotes are not rendered correctly. See: > Once complete, a connection called ?openshift-dev > https://10.1.2.2:8443” > > Good catch. I?ll work on getting that corrected. > > > > Second is just a thought. In the article is debugging done via starting > port forwarding and connecting remote java application. In tooling we have > much more sophisticated way to start debugging. OpenShift 3 Server Adapter > contains a context menu item Debug. Click on the item adds debug port specs > to deployment configuration, starts port forwarding and even attaches a > remote java application. From running application to being debugged > application in one click, if you omit steps to create a server adapter. To > create an OS 3 server adapter just select a service in OpenShift explorer > view and select Server Adapter. It opens wizard with preselected Eclipse > workspace project, OpenShift service etc. So in this way you can create an > adapter just by click on the Finish button. > > That sounds awesome. Do we have documentation supporting this process that > I will be able to use and reference? I would love to provide this in a > follow up post as an alternate option for users. > > > > > Mari?n Labuda > JBoss JBDS QE > > On Thu, Jul 21, 2016 at 8:45 PM, Burr Sutter wrote: > >> FYI >> >> ---------- Forwarded message ---------- >> From: Andrew Block >> Date: Thu, Jul 21, 2016 at 2:26 PM >> Subject: [openshift-sme] Blog post on Debugging Java Application with the >> CDK >> To: openshift-sme >> >> >> Wrote an article on how to debug Java application running in OpenShift in >> the Red Hat Container Development Kit (CDK). This demonstrates a good >> workflow for developers to follow when developing containerized >> applications for deployment in OpenShift utilizing their local environment. >> >> >> http://developers.redhat.com/blog/2016/07/21/debugging-java-applications-using-the-red-hat-container-development-kit/ >> >> >> Enjoy! >> >> >> Andrew Block >> Red Hat Consulting >> 101 N. Wacker, Suite 150 >> Chicago, IL 60606 >> andrew.block at redhat.com | m. (716) 870-2408 >> >> 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 >> >> > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From rwagner at redhat.com Wed Jul 27 12:30:36 2016 From: rwagner at redhat.com (Rick Wagner) Date: Wed, 27 Jul 2016 07:30:36 -0500 Subject: [Devtools] Development suite installer questions In-Reply-To: <34572291.8597672.1469597079861.JavaMail.zimbra@redhat.com> References: <1398019809.5131103.1468300175128.JavaMail.zimbra@redhat.com> <34572291.8597672.1469597079861.JavaMail.zimbra@redhat.com> Message-ID: Hi Denis, Thanks for checking up. The ball is in the customer's court, we haven't heard back for a while. (I left a short note today, asking them how things have worked out.) I've also associated that support case with the new JIRA (thanks for that!) so we can more easily check things between the two. Thanks again, Rick On Wed, Jul 27, 2016 at 12:24 AM, Denis Golovin wrote: > Rick, > > Do you have any update on this case? Was customer able to solve the > problem? > I've opened issue for not setting proper user agent for http requests > in DevSuite installer (see https://issues.jboss.org/browse/JBDS-3979). > > Thanks, > Denis > > ----- Original Message ----- > > From: "Rick Wagner" > > To: "Denis Golovin" > > Cc: devtools at redhat.com > > Sent: Tuesday, July 12, 2016 6:09:20 AM > > Subject: Re: [Devtools] Development suite installer questions > > > > Thanks much for that advice, Denis. > > > > We'll work with the customer to see if this can be used with the browser > > 'whitelist' to enable use of the Development Suite. > > > > Rick > > > > On Tue, Jul 12, 2016 at 12:09 AM, Denis Golovin > wrote: > > > > > Rick, > > > > > > see my comments inline > > > > > > ----- Original Message ----- > > > > From: "Rick Wagner" > > > > To: devtools at redhat.com > > > > Sent: Monday, July 11, 2016 7:20:02 AM > > > > Subject: [Devtools] Development suite installer questions > > > > > > > > Hello DevTools, > > > > > > > > We're working with a customer that brings a few interesting questions > > > about > > > > the installer. > > > > > > > > > > > > Question 1: > > > > > > > > When an attempt is made to download the Development Suite, we see the > > > error: > > > > > > > > "Oops. Something went wrong > > > > The download failed. Please check if you have internet access, > connected > > > to > > > > VPN, have correct configuration for proxy server. Try to download > again > > > > after problem is fixed." > > > > > > > > The user tells us they are behind a proxy server. Do we have any > specific > > > > recommendations for a remedy? > > > > > > I see first problem here is that message doesn't say what exactly went > > > wrong and what installer was trying to download. > > > > > > It could be proxy issue related to: > > > 1. User-Agent header does not set it at all; > > > 2. Download for Vagrant and Oracle Virtualbox uses redirects on > > > developers.redhat.com not direct links see > > > details here https://issues.jboss.org/browse/ORG-2929. > > > > > > Could you ask if links > > > > > > > http://developers.stage.redhat.com/redirect/to/virtualbox-5.0.8.download > > > http://developers.stage.redhat.com/redirect/to/vagrant-1.7.4.download > > > > > > work from browser? > > > > > > > > > > > > > > > Question 2: > > > > > > > > The same user notes that when they do get the installer, it urges > them to > > > > install Cygwin even though it's already present. Is there a way to > avoid > > > > this? > > > > > > Cygwin detection is not implemented yet and it might become optional > > > component to install soon, see supported terminals discussion. > > > > > > Thanks, > > > Denis > > > > > > > > > > > Thanks, > > > > > > > > Rick > > > > > > > > > > > > _______________________________________________ > > > > Devtools mailing list > > > > Devtools at redhat.com > > > > https://www.redhat.com/mailman/listinfo/devtools > > > > > > > > > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From rwagner at redhat.com Wed Jul 27 14:01:17 2016 From: rwagner at redhat.com (Rick Wagner) Date: Wed, 27 Jul 2016 09:01:17 -0500 Subject: [Devtools] CDK fails under QEMU. Have we seen this one before? Message-ID: Hello DevTools SMEs, We have a customer with a failing CDK installation. They appear (we are asking for validation) to be running RHEL 7.2 under QEMU. When they try 'vagrant up', they get the following: "Error while creating domain: Error saving the server: Call to virDomainDefineXML failed: invalid argument: could not find capabilities for domaintype=kvm" Google suggests this error is telling us kvm isn't recognized as a supported feature of the guest o/s. (There are a couple of suggested workarounds, with mixed results.) Before we start poking at it in the customer's environment, we'd like to ask if we have encountered this before ourselves (and if we have a known good remedy). Any hard-won experiences to share? Thanks, Rick -------------- next part -------------- An HTML attachment was scrubbed... URL: From rkratky at redhat.com Wed Jul 27 15:39:43 2016 From: rkratky at redhat.com (Robert Kratky) Date: Wed, 27 Jul 2016 17:39:43 +0200 Subject: [Devtools] CDK fails under QEMU. Have we seen this one before? In-Reply-To: References: Message-ID: <2174180.UeRLbBSLbW@x230> On 27.?7.?2016 09:01:17, Rick Wagner wrote: > Hello DevTools SMEs, > > We have a customer with a failing CDK installation. They appear (we are > asking for validation) to be running RHEL 7.2 under QEMU. > > When they try 'vagrant up', they get the following: > "Error while creating domain: Error saving the server: Call to > virDomainDefineXML failed: invalid argument: could not find capabilities > for domaintype=kvm" > > Google suggests this error is telling us kvm isn't recognized as a > supported feature of the guest o/s. (There are a couple of suggested > workarounds, with mixed results.) > > Before we start poking at it in the customer's environment, we'd like to > ask if we have encountered this before ourselves (and if we have a known > good remedy). Hi Rick, Could it be that the customer forgot to enable nested virtualization? See [1] for how to check for it and set it up. Also, they need to have a host OS that supports it. Fedora does, RHEL does too but only as a TP [2]. Robert [1] https://fedoraproject.org/wiki/How_to_enable_nested_virtualization_in_KVM [2] https://access.redhat.com/solutions/58204 From rwagner at redhat.com Wed Jul 27 16:36:53 2016 From: rwagner at redhat.com (Rick Wagner) Date: Wed, 27 Jul 2016 11:36:53 -0500 Subject: [Devtools] CDK usage: Your thoughts are needed! Message-ID: Hello DevTools SMEs, We are seeing a few more CDK support cases, most seem to indicate curiosity and tire-kicking. We also have a case with a customer going a step further. The customer in question wants to use the CDK to develop on the desktop and deploy to an Enterprise OpenShift. It's my understanding that there are two primary schemes: - Push source code (perhaps using a tag like 'prod') to a source repository accessed by the enterprise OpenShift environment. (Be it QE, Prod, whatever). - Push docker images to an external repository accessed by the enterprise OpenShift. There are nuances like use of WebHooks vs. manual pulls, Jenkins doing the monitoring, etc. This seems a really foundational use case for the CDK, so it seems like something we'd want to document. I've been discussing this with Robert Kratky but wanted to open the discussion to get more viewpoints (and especially more users that have experience.) Of special interest: - The customer is indicating a desire for some widget on the CDK-supplied OpenShift UI so he can 'push' artifacts to the enterprise OpenShift's docker repository. - The customer is asking if Docker version is relevant. (i.e. the CDK's version of Docker may need to align with the external image repository's version. True or False?) Please consider, add thoughts to the discussion. Thank you, Rick -------------- next part -------------- An HTML attachment was scrubbed... URL: From lmohanty at redhat.com Wed Jul 27 17:05:33 2016 From: lmohanty at redhat.com (Lalatendu Mohanty) Date: Wed, 27 Jul 2016 22:35:33 +0530 Subject: [Devtools] CDK fails under QEMU. Have we seen this one before? In-Reply-To: References: Message-ID: <978291c2-c7b6-58da-35c3-41bcb6a524da@redhat.com> On 07/27/2016 07:31 PM, Rick Wagner wrote: > Hello DevTools SMEs, > > We have a customer with a failing CDK installation. They appear (we > are asking for validation) to be running RHEL 7.2 under QEMU. > > When they try 'vagrant up', they get the following: > "Error while creating domain: Error saving the server: Call to > virDomainDefineXML failed: invalid argument: could not find > capabilities for domaintype=kvm" > > Google suggests this error is telling us kvm isn't recognized as a > supported feature of the guest o/s. (There are a couple of suggested > workarounds, with mixed results.) > > Before we start poking at it in the customer's environment, we'd like > to ask if we have encountered this before ourselves (and if we have a > known good remedy). > > Any hard-won experiences to share? Hi, I have seen such errors, but do not exactly remember the reason. But I am fairly sure that this is caused because of incorrect KVM configuration. Some simple things we should check in the setup e.g. 1. Check if the System supports KVM. $grep 'vmx|svm' /proc/cpuinfo 2. Can you run any VM on that machine using KVM? 3. Check if IntelVT or AMD_V virtualization technology is enabled on that machine. If not please enable it in the BIOS [1] [1] https://access.redhat.com/documentation/en-US/Red_Hat_Enterprise_Linux/5/html/Virtualization/sect-Virtualization-Troubleshooting-Enabling_Intel_VT_and_AMD_V_virtualization_hardware_extensions_in_BIOS.html Thanks, Lala > > Thanks, > > Rick > > > _______________________________________________ > Devtools mailing list > Devtools at redhat.com > https://www.redhat.com/mailman/listinfo/devtools -------------- next part -------------- An HTML attachment was scrubbed... URL: From kbsingh at redhat.com Wed Jul 27 17:06:19 2016 From: kbsingh at redhat.com (Karanbir Singh) Date: Wed, 27 Jul 2016 18:06:19 +0100 Subject: [Devtools] CDK fails under QEMU. Have we seen this one before? In-Reply-To: References: Message-ID: <8e0dc685-6daf-9185-f028-6cc9f615c837@redhat.com> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 27/07/16 15:01, Rick Wagner wrote: > Hello DevTools SMEs, > > We have a customer with a failing CDK installation. They appear > (we are asking for validation) to be running RHEL 7.2 under QEMU. > > When they try 'vagrant up', they get the following: "Error while > creating domain: Error saving the server: Call to > virDomainDefineXML failed: invalid argument: could not find > capabilities for domaintype=kvm" > > Google suggests this error is telling us kvm isn't recognized as a > supported feature of the guest o/s. (There are a couple of > suggested workarounds, with mixed results.) > > Before we start poking at it in the customer's environment, we'd > like to ask if we have encountered this before ourselves (and if we > have a known good remedy). > > Any hard-won experiences to share? Vagrant when using the libvirt backend will default to using kvm, if the user does not have perms ( eg. the virsh create command will ask for the root passwd ), or have the kvm perms relaxed so the user can create the domain - this is going to fail. Essentially, the virt stack is offloaded to libvirt ( with assumptions ) - and changes in there will need to be validated by the user themselves. if the user is trying to use emulated qemu setup ( ie, just qemu and not qemu-kvm ) vagrant will fail as well. We've had a few people come around asking about this on the centos channels recently, including trying to run vagrant with xen backends, which are not supported by vagrant itself. regards - -- Karanbir Singh, Project Lead, The CentOS Project, London, UK Red Hat Ext. 8274455 | DID: 0044 207 009 4455 -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (GNU/Linux) iQEcBAEBAgAGBQJXmOoLAAoJEI3Oi2Mx7xbt4FsH/3ABBZPybQ5spZJNTAmzdozD YOBCbJYYJaUaR5gR5I90eyhyu+2JzZpYfteb2ZZ25aeGgiDYv2NLicGCdoOrMum3 eoAFZq3/3I2YOdAN7B71fiV6PPSCdSFy14AfwDgSI330eBDnm7j0rgHUcQvCW9Fc PPEVcZigVqWdIrugKABuW7/DgKOPWLmXCvcXWxTy3erhBg0u7I/sf3w4CQgRzEhe 1Hp+l1LotOwdlifDwsl6FvJFvA+gEq/laF2i+fy6dB9EQmkWM+IBt6efDIya9Fo4 LB9DOudUIGlGNuJIBy8JfXnme7ivHww5Hw/FyvUmJLp3I+axeRSYEj2n2FXVZZA= =k5V4 -----END PGP SIGNATURE----- From rwagner at redhat.com Wed Jul 27 18:08:43 2016 From: rwagner at redhat.com (Rick Wagner) Date: Wed, 27 Jul 2016 13:08:43 -0500 Subject: [Devtools] CDK fails under QEMU. Have we seen this one before? In-Reply-To: <2174180.UeRLbBSLbW@x230> References: <2174180.UeRLbBSLbW@x230> Message-ID: Thanks for that, Robert. We'll run it down with the customer to see if these are applicable.* Rick * Interesting side note: In most of our middleware support arenas, support involves pinning down a bug that is replicated on the JVM and mitigated with a framework code change. Thus far, CDK support is turning out to be more about environmental issues. CEE will look for ways to recognize best practices and optimize.... On Wed, Jul 27, 2016 at 10:39 AM, Robert Kratky wrote: > On 27.?7.?2016 09:01:17, Rick Wagner wrote: > > > Hello DevTools SMEs, > > > > We have a customer with a failing CDK installation. They appear (we are > > asking for validation) to be running RHEL 7.2 under QEMU. > > > > When they try 'vagrant up', they get the following: > > "Error while creating domain: Error saving the server: Call to > > virDomainDefineXML failed: invalid argument: could not find capabilities > > for domaintype=kvm" > > > > Google suggests this error is telling us kvm isn't recognized as a > > supported feature of the guest o/s. (There are a couple of suggested > > workarounds, with mixed results.) > > > > Before we start poking at it in the customer's environment, we'd like to > > ask if we have encountered this before ourselves (and if we have a known > > good remedy). > > Hi Rick, > > Could it be that the customer forgot to enable nested virtualization? See > [1] for how to check for it and set it up. > > Also, they need to have a host OS that supports it. Fedora does, RHEL does > too but only as a TP [2]. > > Robert > > [1] > https://fedoraproject.org/wiki/How_to_enable_nested_virtualization_in_KVM > [2] https://access.redhat.com/solutions/58204 > -------------- next part -------------- An HTML attachment was scrubbed... URL: From cdrage at redhat.com Wed Jul 27 20:33:56 2016 From: cdrage at redhat.com (Charlie Drage) Date: Wed, 27 Jul 2016 16:33:56 -0400 Subject: [Devtools] Atomic App 0.6.2 Release! Message-ID: <20160727203356.GB1@b11a20d7c9ca> Hey all! We've gone ahead and released Atomic App 0.6.2 Here is a general overview on the release (which can also be found at http://www.projectatomic.io/blog/2016/07/atomic-app-0-6-2-release/ This release of Atomic App introduces the new `atomicapp index` command. We add this command in order to give a quick overview of all available featured and tested Nuleculized applications on [github.com/projectatomic/nulecule-library](https://github.com/projectatomic/nulecule-library). The ability to generate your own list is available as well with the `atomicapp index generate` command. The main features of this release are: * Addition of the `atomicapp index` command * Correct file permissions are now when extracting Nuleculized containers * OpenShift connection issue bugfix ## `atomicapp index` This release adds the addition of the `atomicapp index` command. By using the `atomicapp index list` command, Atomic App will retrieve a container containing a valid `index.yml` and output all available Nulecule containers. This index can also be updated by using `atomicapp index update`. **atomicapp index list** Outputs the list of available containers located at `~/.atomicapp/index.yml`. ``` ? atomicapp index list INFO :: Atomic App: 0.6.2 - Mode: Index ID VER PROVIDERS LOCATION postgresql-atomicapp 1.0.0 {D,O,K} docker.io/projectatomic/postgresql-centos7-atomicapp flask_redis_nulecule 0.0.1 {D,K} docker.io/projectatomic/flask-redis-centos7-atomicapp redis-atomicapp 0.0.1 {D,O,K} docker.io/projectatomic/redis-centos7-atomicapp gocounter 0.0.1 {D,K} docker.io/projectatomic/gocounter-scratch-atomicapp mariadb-atomicapp 1.0.0 {D,O,K} docker.io/projectatomic/mariadb-centos7-atomicapp helloapache-app 0.0.1 {D,K,M} docker.io/projectatomic/helloapache mongodb-atomicapp 1.0.0 {D,O,K} docker.io/projectatomic/mongodb-centos7-atomicapp etherpad-app 0.0.1 {D,O,K} docker.io/projectatomic/etherpad-centos7-atomicapp apache-centos7-atomicapp 0.0.1 {D,K,M} docker.io/projectatomic/apache-centos7-atomicapp wordpress-atomicapp 2.0.0 {D,O,K} docker.io/projectatomic/wordpress-centos7-atomicapp skydns-atomicapp 0.0.1 {K} docker.io/projectatomic/skydns-atomicapp guestbookgo-atomicapp 0.0.1 {O,K} docker.io/projectatomic/guestbookgo-atomicapp mariadb-app 0.0.1 {D,K} docker.io/projectatomic/mariadb-fedora-atomicapp gitlab-atomicapp 1.2.0 {D,K} docker.io/projectatomic/gitlab-centos7-atomicapp ``` **atomicapp index update** Updates the `index.yml` file. ``` ? atomicapp index update INFO :: Atomic App: 0.6.2 - Mode: Index INFO :: Updating the index list INFO :: Pulling latest index image... INFO :: Skipping pulling docker image: projectatomic/nulecule-library INFO :: Copying files from image projectatomic/nulecule-library:/index.yaml to /home/wikus/.atomicapp/index.yaml INFO :: Index updated ``` **atomicapp index generate** Generates a valid `index.yml` file to use in listing all available containers. ``` ? atomicapp index generate ./nulecule-library INFO :: Atomic App: 0.6.1 - Mode: Index INFO :: Generating index.yaml from ./nulecule-library INFO :: index.yaml generated ``` ``` Abhishek (3): incorrect_log_level Show help when no arguments given. raise DockerException for docker commands Charlie Drage (7): Remove warning in regards to application-entity Refactor extracting Fixes connecting issues with OpenShift Fix coverage Modifies asking for parameters to show app name When fetching or extracting, set the correct uid + guid Add "index" command to Atomic App Shubham Minglani (1): collect only atomicapp tests ``` -- Charlie Drage Red Hat - Dev Tools / Project Atomic PGP - 4096R/C037D617 http://pgp.mit.edu/pks/lookup?op=get&search=0xDA227403C037D617 From kbsingh at redhat.com Thu Jul 28 15:34:21 2016 From: kbsingh at redhat.com (Karanbir Singh) Date: Thu, 28 Jul 2016 16:34:21 +0100 Subject: [Devtools] Current Vagrant is broken ( 1.8.5 ) Message-ID: -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 hi https://github.com/mitchellh/vagrant/issues/7610 The current vagrant release is broken for all linux distro's, due to bad perms set on the vagrant auth key injected at VM instance bringup. Fix is in 1.8.6, but for the time being there is no info on when that release will happen. Therefore the only option is to downgrade to 1.8.4 if this issue impacts you. regards - -- Karanbir Singh, Project Lead, The CentOS Project, London, UK Red Hat Ext. 8274455 | DID: 0044 207 009 4455 -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (GNU/Linux) iQEcBAEBAgAGBQJXmiX9AAoJEI3Oi2Mx7xbteoQIAMuaNWY4JdpjxnXhaGaOHFOb qmMzFtJbNPtQWlvGiU85vLhmx89c2Q0epRZyAJH1Lx93HvMK0wWNo9kGyVeMjjeh JxkUJbAk8ODZVyEBfHeQR0SI3sNB7o4k8ACnN36N6mMpWA2HSWfvXuLmS/M4DeXJ QSUym+1VndFW6EWQNw6N+8WqEbIqH7EmHIQ9Qe3j+pwPRnyC25velxE/8XOIWrhh VICds6dvJOkIc+GW/TVjsT1pGbcsxeP2iP0dn5hdlcW0wBRhLI3rQMl51KGBtgK5 U5yvZsEu3w3K499CfBRgcXEbtYmHhDyNIr9ayrwVOAH5ccN1p/i3WpUwi9UIhvs= =YIL8 -----END PGP SIGNATURE----- From bgurung at redhat.com Thu Jul 28 17:19:29 2016 From: bgurung at redhat.com (Budh Gurung) Date: Thu, 28 Jul 2016 22:49:29 +0530 Subject: [Devtools] Current Vagrant is broken ( 1.8.5 ) In-Reply-To: References: Message-ID: Hi, On Thu, Jul 28, 2016 at 9:04 PM, Karanbir Singh wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > hi > > https://github.com/mitchellh/vagrant/issues/7610 > > The current vagrant release is broken for all linux distro's, due to > bad perms set on the vagrant auth key injected at VM instance bringup. > > Fix is in 1.8.6, but for the time being there is no info on when that > release will happen. Therefore the only option is to downgrade to > 1.8.4 if this issue impacts you. > > Thanks KB for bring it up and notifying us. We thought 1.8.5 has fix of installing plugin with local gem [1] but with your notification we will not recommend ADB users to upgrade vagrant to 1.8.5. Currently, the recommended vagrant version is 1.7.4. However, latest vagrant support is being tracked here [2] and we will continue looking for stable version and verify it and upgrade our recommended vagrant version for ADB. regards > > - -- > Karanbir Singh, Project Lead, The CentOS Project, London, UK > Red Hat Ext. 8274455 | DID: 0044 207 009 4455 > -----BEGIN PGP SIGNATURE----- > Version: GnuPG v2.0.22 (GNU/Linux) > > iQEcBAEBAgAGBQJXmiX9AAoJEI3Oi2Mx7xbteoQIAMuaNWY4JdpjxnXhaGaOHFOb > qmMzFtJbNPtQWlvGiU85vLhmx89c2Q0epRZyAJH1Lx93HvMK0wWNo9kGyVeMjjeh > JxkUJbAk8ODZVyEBfHeQR0SI3sNB7o4k8ACnN36N6mMpWA2HSWfvXuLmS/M4DeXJ > QSUym+1VndFW6EWQNw6N+8WqEbIqH7EmHIQ9Qe3j+pwPRnyC25velxE/8XOIWrhh > VICds6dvJOkIc+GW/TVjsT1pGbcsxeP2iP0dn5hdlcW0wBRhLI3rQMl51KGBtgK5 > U5yvZsEu3w3K499CfBRgcXEbtYmHhDyNIr9ayrwVOAH5ccN1p/i3WpUwi9UIhvs= > =YIL8 > -----END PGP SIGNATURE----- > > _______________________________________________ > Devtools mailing list > Devtools at redhat.com > https://www.redhat.com/mailman/listinfo/devtools [1] https://github.com/mitchellh/vagrant/issues/7493 [2] https://github.com/projectatomic/vagrant-service-manager/issues/294 Regards, Budh Ram Gurung Software Engineer - Dev Tools -------------- next part -------------- An HTML attachment was scrubbed... URL: From dusty at dustymabe.com Thu Jul 28 19:25:24 2016 From: dusty at dustymabe.com (Dusty Mabe) Date: Thu, 28 Jul 2016 15:25:24 -0400 Subject: [Devtools] vagrant-sshfs pre-release testing Message-ID: Please take a moment to test out the pre-release of the next version of vagrant-sshfs. This version has the fixes for windows issues that we found right before the release of CDK 2.1. Here is how to test: vagrant plugin uninstall vagrant-sshfs wget https://dustymabe.fedorapeople.org/gem/vagrant-sshfs-1.1.0.dev.gem vagrant plugin install ./vagrant-sshfs-1.1.0.dev.gem Thanks Dusty From budhram.gurung01 at gmail.com Fri Jul 29 05:06:59 2016 From: budhram.gurung01 at gmail.com (Budh Ram) Date: Fri, 29 Jul 2016 10:36:59 +0530 Subject: [Devtools] vagrant-sshfs pre-release testing In-Reply-To: References: Message-ID: Hi Dusty, On Fri, Jul 29, 2016 at 12:55 AM, Dusty Mabe wrote: > > Please take a moment to test out the pre-release of the next version of > vagrant-sshfs. > > This version has the fixes for windows issues that we found right before > the release of CDK 2.1. > Great. Finally we have fix for that awful issue. Will definitely test it. > Here is how to test: > > vagrant plugin uninstall vagrant-sshfs > wget https://dustymabe.fedorapeople.org/gem/vagrant-sshfs-1.1.0.dev.gem > vagrant plugin install ./vagrant-sshfs-1.1.0.dev.gem > Thanks for providing get start with testing steps. It will surely help. > Thanks > Dusty > > _______________________________________________ > Devtools mailing list > Devtools at redhat.com > https://www.redhat.com/mailman/listinfo/devtools > -- Regards, Budh Ram Gurung -------------- next part -------------- An HTML attachment was scrubbed... URL: From mmalina at redhat.com Fri Jul 29 10:28:20 2016 From: mmalina at redhat.com (Martin Malina) Date: Fri, 29 Jul 2016 12:28:20 +0200 Subject: [Devtools] vagrant-sshfs pre-release testing In-Reply-To: References: Message-ID: > On 28. 7. 2016, at 21:25, Dusty Mabe wrote: > > > Please take a moment to test out the pre-release of the next version of vagrant-sshfs. Hi, I tested this on Mac and it works correctly - at least in the sense that I can start this successfully in jboss tools 4.4.1.AM2 (I used components/rhel/misc/shared_folder/rhel-ose/VagrantFile and the supplied sshfs gem). I haven't tested on Windows though and I won't be able to until next week. > > This version has the fixes for windows issues that we found right before the release of CDK 2.1. I would like to correct this. The issue prevented startup of cdk in devstudio on all platforms, not just Windows. There was a quickfix provided in CDK 2.1 RC4 which fixed this on Linux and Mac, but it was reverted for RC5=GA. See here for details: https://issues.jboss.org/browse/JBIDE-22604?focusedCommentId=13253941&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-13253941 -Martin > > Here is how to test: > > vagrant plugin uninstall vagrant-sshfs > wget https://dustymabe.fedorapeople.org/gem/vagrant-sshfs-1.1.0.dev.gem > vagrant plugin install ./vagrant-sshfs-1.1.0.dev.gem > > Thanks > Dusty > > _______________________________________________ > 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 Fri Jul 29 18:50:50 2016 From: lmohanty at redhat.com (Lalatendu Mohanty) Date: Sat, 30 Jul 2016 00:20:50 +0530 Subject: [Devtools] CDK usage: Your thoughts are needed! In-Reply-To: References: Message-ID: <6332b615-a44f-4de4-cbaa-5a100c1899ba@redhat.com> On 07/27/2016 10:06 PM, Rick Wagner wrote: > Hello DevTools SMEs, > > We are seeing a few more CDK support cases, most seem to indicate > curiosity and tire-kicking. We also have a case with a customer going > a step further. > > The customer in question wants to use the CDK to develop on the > desktop and deploy to an Enterprise OpenShift. > > It's my understanding that there are two primary schemes: > > - Push source code (perhaps using a tag like 'prod') to a source > repository accessed by the enterprise OpenShift environment. (Be it > QE, Prod, whatever). > - Push docker images to an external repository accessed by the > enterprise OpenShift. > These ideas perfectly makes sense to me. Any organization going through the DevOps route would need this work flows. > There are nuances like use of WebHooks vs. manual pulls, Jenkins doing > the monitoring, etc. > > This seems a really foundational use case for the CDK, so it seems > like something we'd want to document. I've been discussing this with > Robert Kratky but wanted to open the discussion to get more viewpoints > (and especially more users that have experience.) These needs to ironed out , needs testing and then documentation. > > Of special interest: > > - The customer is indicating a desire for some widget on the > CDK-supplied OpenShift UI so he can 'push' artifacts to the enterprise > OpenShift's docker repository. +1 . Developer tool should help move things in to the DevOps workflow. The pipeline work going on in OpenShift might align here. Need to cross check. > - The customer is asking if Docker version is relevant. (i.e. the > CDK's version of Docker may need to align with the external image > repository's version. True or False?) The only requirement I think is the docker version should support the image format present in external image repository. I do not think this would be problem if they stick to OpenShift Enterprise. > > Please consider, add thoughts to the discussion. > > Thank you, > > Rick > > > _______________________________________________ > Devtools mailing list > Devtools at redhat.com > https://www.redhat.com/mailman/listinfo/devtools -------------- next part -------------- An HTML attachment was scrubbed... URL: