[JBoss JIRA] (JBDS-3627) Installer needs to help move past lack of t/c signing
by Denis Golovin (JIRA)
[ https://issues.jboss.org/browse/JBDS-3627?page=com.atlassian.jira.plugin.... ]
Denis Golovin closed JBDS-3627.
-------------------------------
Fix Version/s: 11.2.0.AM3
(was: 11.x)
Resolution: Migrated to another ITS
Moved to https://github.com/redhat-developer-tooling/developer-platform-install/is....
> Installer needs to help move past lack of t/c signing
> -----------------------------------------------------
>
> Key: JBDS-3627
> URL: https://issues.jboss.org/browse/JBDS-3627
> Project: Red Hat JBoss Developer Studio (devstudio)
> Issue Type: Epic
> Components: platform-installer
> Affects Versions: 10.0.0.GA
> Reporter: Joshua Wilson
> Assignee: Denis Golovin
> Labels: havoc
> Fix For: 11.2.0.AM3
>
> Attachments: Installer-not-signed-tc.PNG
>
>
> DevSuite installer uses "REST services in JBoss Download Manager" explained here https://mojo.redhat.com/docs/DOC-940689.
> DevSuite Intsaller follows the explanation for tc-accepted entry point [code is here|https://github.com/redhat-developer-tooling/developer-platform-insta...]. It uses file from previous CDK release (published in cdn and available through download manager) to do verification:
> 1. that provided credentials are valid;
> 2. that required T&C's are signed.
> There are two major use cases for developers installing DevSuite using Installer:
> 1. Direct download - when developer sign in to developers.redhat.com and download installer himeslf;
> 2. Shared installer - when someone share installer with developers without account.
> There two kind of users involved in those scenarios above:
> 1. New users that must go through registration process;
> 2. Registered users.
> *Direct download*
> For new ones registration process is really simple now. After creating RHD account and downloading installer there is no additional steps to get through installation.
> For already registered users there could be problems related to T&C's and authentication reported here https://issues.jboss.org/browse/RHDENG-579.
> So far there are two kind of problems:
> 1. Users can login and download DevSuite installer, but cannot use the same credentials to install;
> 2. Users that can login in to developers.redhat.com and get request to sign additional T&C's but credentials for the same user in DevSuite Installer reported as invalid when REST tc-accepted entry point is used
> *Shared Download*
> In this scenario new users without account can press Register link, then go through registration process in browser return back to installer and use new account credentials for installation.
> Registered users could need to sign additional T&C's if missing and would be good to show external link to do so. Current entry point tc-accepted does not provide any hints where missing T&C's could be signed.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 3 months
[JBoss JIRA] (JBDS-4063) Report Validation Errors regardless components selected for installation
by Denis Golovin (JIRA)
[ https://issues.jboss.org/browse/JBDS-4063?page=com.atlassian.jira.plugin.... ]
Denis Golovin closed JBDS-4063.
-------------------------------
Fix Version/s: 11.2.0.AM3
(was: 11.x)
Resolution: Migrated to another ITS
Moved to https://github.com/redhat-developer-tooling/developer-platform-install/is...
> Report Validation Errors regardless components selected for installation
> ------------------------------------------------------------------------
>
> Key: JBDS-4063
> URL: https://issues.jboss.org/browse/JBDS-4063
> Project: Red Hat JBoss Developer Studio (devstudio)
> Issue Type: Feature Request
> Components: platform-installer
> Affects Versions: 10.1.0.GA
> Reporter: Denis Golovin
> Assignee: Denis Golovin
> Labels: ui
> Fix For: 11.2.0.AM3
>
>
> During installation installer should verify that several prerequisites are met in general for whole installer, examples are:
> 1. Verification for platform architecture 32-bit/64-bit (there is no verification for that yet);
> 2. Physical memory installed more than minimal amount required where minimum amount is calculated from across all stack components available for installation;
> 3. The same applies to disk space;
> 4. Internet access to download required components for online iunstaller.
> For problems like this currently there is no suitable page to show in installer.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 3 months
[JBoss JIRA] (JBDS-4339) DevSuite installer on Windows should ask for hostfolder details
by Denis Golovin (JIRA)
[ https://issues.jboss.org/browse/JBDS-4339?page=com.atlassian.jira.plugin.... ]
Denis Golovin closed JBDS-4339.
-------------------------------
Fix Version/s: 11.2.0.AM3
(was: 11.x)
Resolution: Done
Moved to https://github.com/redhat-developer-tooling/developer-platform-install/is...
> DevSuite installer on Windows should ask for hostfolder details
> ---------------------------------------------------------------
>
> Key: JBDS-4339
> URL: https://issues.jboss.org/browse/JBDS-4339
> Project: Red Hat JBoss Developer Studio (devstudio)
> Issue Type: Enhancement
> Components: platform-installer
> Reporter: Hardy Ferentschik
> Assignee: Denis Golovin
> Fix For: 11.2.0.AM3
>
>
> Minishift/CDK allows to mount a Samba/CIFS share into the VM. This is a replacement for the current approach of using vagrant-sshfs as part of ADB/CDK 2.x.
> The vagrant-sshfs approach was password free, but for the CIFS approach we at the very least need the users Windows password. On top of this we can also allow the user to specify any share (opposed to just this home directory) as well as a custom mount point in the VM.
> The question is where and how the user specifies this information. In order to have a fully integrated solution where after the install DevStudio can be launched and the CDK adapter starting the CDK, the installer would need to ask the user for the required information and write some additional configuration data.
> Without this additional setup, the user would not have any host folders available. They can be added later by running a {code}minishift{code} command, but this would be a manual step and it might not be obvious to the user.
> Thoughts?
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 3 months
[JBoss JIRA] (JBDS-3841) Installer Sets Path for Wrong User
by Denis Golovin (JIRA)
[ https://issues.jboss.org/browse/JBDS-3841?page=com.atlassian.jira.plugin.... ]
Denis Golovin closed JBDS-3841.
-------------------------------
Fix Version/s: 11.2.0.AM3
(was: 11.x)
Resolution: Migrated to another ITS
Moved to github here https://github.com/redhat-developer-tooling/developer-platform-install/is...
> Installer Sets Path for Wrong User
> ----------------------------------
>
> Key: JBDS-3841
> URL: https://issues.jboss.org/browse/JBDS-3841
> Project: Red Hat JBoss Developer Studio (devstudio)
> Issue Type: Bug
> Components: platform-installer
> Affects Versions: 9.1.0.GA
> Environment: Windows 10
> Reporter: Thomas Mäder
> Assignee: Denis Golovin
> Priority: Critical
> Labels: user-docs
> Fix For: 11.2.0.AM3
>
>
> When I run the offline installer from my non-privileged account, I am prompted by UAC for an administrator login. When I enter my admin login and proceed, tools like vagrant, etc. will not be available from the command line in my non-privileged account. It turns out, the necessary path entries were added to the user-specific path of the admin user, not the user starting the installer.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 3 months
[JBoss JIRA] (JBDS-3965) Add a note on how to launch cdk in last page of devsuite installer
by Denis Golovin (JIRA)
[ https://issues.jboss.org/browse/JBDS-3965?page=com.atlassian.jira.plugin.... ]
Denis Golovin closed JBDS-3965.
-------------------------------
Resolution: Migrated to another ITS
Moved to https://github.com/redhat-developer-tooling/developer-platform-install/is...
> Add a note on how to launch cdk in last page of devsuite installer
> ------------------------------------------------------------------
>
> Key: JBDS-3965
> URL: https://issues.jboss.org/browse/JBDS-3965
> Project: Red Hat JBoss Developer Studio (devstudio)
> Issue Type: Feature Request
> Components: platform-installer
> Affects Versions: 10.1.0.AM2
> Reporter: Martin Malina
> Assignee: Denis Golovin
> Fix For: 11.2.0.AM3
>
>
> Recently, [~rick_wagner] gave us some feedback on how he tried to use the devsuite installer and then connect to the docker daemon running in cdk.
> This is described here: JBIDE-22734
> What happened was that Rick didn't know he was supposed to start CDK from the Servers view. Having some prior knowledge of CDK, he started it from CLI. Then he went to the Docker Explorer view and wanted to connect to cdk's docker daemon.
> Normally, the docker connection will be created for you automatically, but that assumes you start the cdk adapter in Servers View.
> So here's a proposal:
> Perhaps at the end of the devsuite installer, just before devstudio is launched, we could briefly note that to start using CDK, you can start it from the Server view, once devstudio is launched?
> Please note that the actual name of the server adapter is probably Container Runtime Environment, but I'm not 100 % sure, this needs to be verified.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 3 months