[jira] [Created] (AIRAVATA-2583) Group based Compute Resource Profiles
Suresh Marru created AIRAVATA-2583: -- Summary: Group based Compute Resource Profiles Key: AIRAVATA-2583 URL: https://issues.apache.org/jira/browse/AIRAVATA-2583 Project: Airavata Issue Type: New Feature Affects Versions: 0.17 Reporter: Suresh Marru Assignee: Sachin Kariyattin Priority: Normal Airavata tenants using gateways for education would like to enforce granular resource restrictions. An example would be having students restricted to smaller scale resource limits, researchers ability to user larger number of resources. This task requires: * Defining thrift data models * Create JPA classes and test coverage * Create CPI methods to access these group preferences -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (AIRAVATA-2554) Admin dashboard customization
[ https://issues.apache.org/jira/browse/AIRAVATA-2554?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16238643#comment-16238643 ] ASF subversion and git services commented on AIRAVATA-2554: --- Commit b73cf69fededb98cf7d17cf5ed86f19fa97d7f39 in airavata's branch refs/heads/develop from [~smarru] [ https://gitbox.apache.org/repos/asf?p=airavata.git;h=b73cf69 ] Merge pull request #130 from sachinkariyattin/develop [AIRAVATA-2554] Admin dashboard customization - thanks @sachinkariyattin for your contribution, this is good to be merged. > Admin dashboard customization > - > > Key: AIRAVATA-2554 > URL: https://issues.apache.org/jira/browse/AIRAVATA-2554 > Project: Airavata > Issue Type: Improvement > Components: PGA PHP Web Gateway >Affects Versions: 0.17 >Reporter: Sachin Kariyattin >Assignee: Sachin Kariyattin >Priority: Major > > Currently there is no provision for admins to customize the dashboard to view > the experiment details. > Goal: To implement dashboard customization feature so that gateway admins > will be able to view flexible statistics -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (AIRAVATA-2279) Gateway credential store UI also to have the same format as individual user settings
[
https://issues.apache.org/jira/browse/AIRAVATA-2279?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16238433#comment-16238433
]
ASF GitHub Bot commented on AIRAVATA-2279:
--
stephenpaul2727 commented on a change in pull request #75: [AIRAVATA-2279 &
2280] FIXED.
URL:
https://github.com/apache/airavata-php-gateway/pull/75#discussion_r148898718
##
File path: app/views/admin/manage-credentials.blade.php
##
@@ -113,34 +134,38 @@ class="sr-only">Close
@endif
-
-
-
-Token
-
-Description
-@if( Session::has("admin"))
-Delete
-@endif
-
-
-@foreach( $pwdTokens as $token => $publicKey)
-
-
-{{ $token }}
-
-
-{{ $publicKey }}
-
-@if( Session::has("admin"))
-
-
-
-@endif
-
+
+@foreach ($pwdTokens as $token => $publicKey)
Review comment:
This is the pre-existing variable format. Yes, this is confusing. I'll fix
it.
This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
> Gateway credential store UI also to have the same format as individual user
> settings
>
>
> Key: AIRAVATA-2279
> URL: https://issues.apache.org/jira/browse/AIRAVATA-2279
> Project: Airavata
> Issue Type: Bug
> Components: PGA PHP Web Gateway
> Environment: dev.seagrid.org
>Reporter: Eroma
>Assignee: Marcus Christie
>Priority: Major
> Fix For: 0.18
>
>
> Currently there are no description ora copy button to copy the public key in
> gateway credential store.
> Unifying the UI with User settings will make it easy for the gateway admins.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (AIRAVATA-2279) Gateway credential store UI also to have the same format as individual user settings
[
https://issues.apache.org/jira/browse/AIRAVATA-2279?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16238430#comment-16238430
]
ASF GitHub Bot commented on AIRAVATA-2279:
--
stephenpaul2727 commented on a change in pull request #75: [AIRAVATA-2279 &
2280] FIXED.
URL:
https://github.com/apache/airavata-php-gateway/pull/75#discussion_r148898439
##
File path: app/controllers/AdminController.php
##
@@ -421,33 +434,36 @@ public function getExperimentsOfTimeRange()
}
public function createSSH(){
- $newToken = AdminUtilities::create_ssh_token_for_gateway(null);
+$description = Input::get("description");
+if($description == "Default SSH Key"){
Review comment:
Admins cannot create two keys with the same description. I'm doing this on
client side using jQuery.
This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
> Gateway credential store UI also to have the same format as individual user
> settings
>
>
> Key: AIRAVATA-2279
> URL: https://issues.apache.org/jira/browse/AIRAVATA-2279
> Project: Airavata
> Issue Type: Bug
> Components: PGA PHP Web Gateway
> Environment: dev.seagrid.org
>Reporter: Eroma
>Assignee: Marcus Christie
>Priority: Major
> Fix For: 0.18
>
>
> Currently there are no description ora copy button to copy the public key in
> gateway credential store.
> Unifying the UI with User settings will make it easy for the gateway admins.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (AIRAVATA-2279) Gateway credential store UI also to have the same format as individual user settings
[
https://issues.apache.org/jira/browse/AIRAVATA-2279?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16238432#comment-16238432
]
ASF GitHub Bot commented on AIRAVATA-2279:
--
stephenpaul2727 commented on a change in pull request #75: [AIRAVATA-2279 &
2280] FIXED.
URL:
https://github.com/apache/airavata-php-gateway/pull/75#discussion_r148898495
##
File path: app/controllers/AdminController.php
##
@@ -345,9 +345,22 @@ public function deleteRole(){
public function credentialStoreView(){
Session::put("admin-nav", "credential-store");
-$tokens = AdminUtilities::get_all_ssh_tokens();
+$tokens = AdminUtilities::get_all_ssh_tokens_with_description();
+//Auto-generating the Default SSH Key if there is no key with such
description.
Review comment:
Hi Marcus,
The reason why I'm doing this is if this code is pushed live, most of the
people might not have key with description "default SSH Key". As this key is
supposed to be default, I'm creating one for them. If a default key is not
necessary, I'll remove this!
Thanks
This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
> Gateway credential store UI also to have the same format as individual user
> settings
>
>
> Key: AIRAVATA-2279
> URL: https://issues.apache.org/jira/browse/AIRAVATA-2279
> Project: Airavata
> Issue Type: Bug
> Components: PGA PHP Web Gateway
> Environment: dev.seagrid.org
>Reporter: Eroma
>Assignee: Marcus Christie
>Priority: Major
> Fix For: 0.18
>
>
> Currently there are no description ora copy button to copy the public key in
> gateway credential store.
> Unifying the UI with User settings will make it easy for the gateway admins.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (AIRAVATA-2279) Gateway credential store UI also to have the same format as individual user settings
[
https://issues.apache.org/jira/browse/AIRAVATA-2279?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16238405#comment-16238405
]
ASF GitHub Bot commented on AIRAVATA-2279:
--
machristie commented on a change in pull request #75: [AIRAVATA-2279 & 2280]
FIXED.
URL:
https://github.com/apache/airavata-php-gateway/pull/75#discussion_r148895633
##
File path: app/views/admin/manage-credentials.blade.php
##
@@ -113,34 +134,38 @@ class="sr-only">Close
@endif
-
-
-
-Token
-
-Description
-@if( Session::has("admin"))
-Delete
-@endif
-
-
-@foreach( $pwdTokens as $token => $publicKey)
-
-
-{{ $token }}
-
-
-{{ $publicKey }}
-
-@if( Session::has("admin"))
-
-
-
-@endif
-
+
+@foreach ($pwdTokens as $token => $publicKey)
+
+
+
+{{{ $publicKey }}}
+
+
+
+
+
+
+
+
+Copy
+
+
+
+
+
+Delete
Review comment:
Let's not do anything special with passwords based on their description.
This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
> Gateway credential store UI also to have the same format as individual user
> settings
>
>
> Key: AIRAVATA-2279
> URL: https://issues.apache.org/jira/browse/AIRAVATA-2279
> Project: Airavata
> Issue Type: Bug
> Components: PGA PHP Web Gateway
> Environment: dev.seagrid.org
>Reporter: Eroma
>Assignee: Marcus Christie
>Priority: Major
> Fix For: 0.18
>
>
> Currently there are no description ora copy button to copy the public key in
> gateway credential store.
> Unifying the UI with User settings will make it easy for the gateway admins.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (AIRAVATA-2279) Gateway credential store UI also to have the same format as individual user settings
[
https://issues.apache.org/jira/browse/AIRAVATA-2279?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16238408#comment-16238408
]
ASF GitHub Bot commented on AIRAVATA-2279:
--
machristie commented on a change in pull request #75: [AIRAVATA-2279 & 2280]
FIXED.
URL:
https://github.com/apache/airavata-php-gateway/pull/75#discussion_r148894369
##
File path: app/controllers/AdminController.php
##
@@ -421,33 +434,36 @@ public function getExperimentsOfTimeRange()
}
public function createSSH(){
- $newToken = AdminUtilities::create_ssh_token_for_gateway(null);
+$description = Input::get("description");
+if($description == "Default SSH Key"){
Review comment:
I don't think this check is necessary.
On the other hand, it might be nice to prevent admins from creating two keys
with the same description.
This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
> Gateway credential store UI also to have the same format as individual user
> settings
>
>
> Key: AIRAVATA-2279
> URL: https://issues.apache.org/jira/browse/AIRAVATA-2279
> Project: Airavata
> Issue Type: Bug
> Components: PGA PHP Web Gateway
> Environment: dev.seagrid.org
>Reporter: Eroma
>Assignee: Marcus Christie
>Priority: Major
> Fix For: 0.18
>
>
> Currently there are no description ora copy button to copy the public key in
> gateway credential store.
> Unifying the UI with User settings will make it easy for the gateway admins.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (AIRAVATA-2279) Gateway credential store UI also to have the same format as individual user settings
[
https://issues.apache.org/jira/browse/AIRAVATA-2279?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16238404#comment-16238404
]
ASF GitHub Bot commented on AIRAVATA-2279:
--
machristie commented on a change in pull request #75: [AIRAVATA-2279 & 2280]
FIXED.
URL:
https://github.com/apache/airavata-php-gateway/pull/75#discussion_r148895045
##
File path: app/views/admin/manage-credentials.blade.php
##
@@ -15,58 +15,79 @@
@if( Session::has("message"))
-
-
-Close
-{{ Session::get("message") }}
-
+
+Close
+{{{ Session::get("message") }}}
{{ Session::forget("message") }}
@endif
+@if( Session::has("error-message"))
+
+Close
+{{{ Session::get("error-message") }}}
+
+{{ Session::forget("error-message") }}
+@endif
+
SSH Keys
+
+
@if(Session::has("admin"))
-
-
-
-Generate a new token
-
-
-
-
-
+
+
+Generate New SSH Key
+
+
+
+
+Description for new SSH key
+
+
+Generate
+
+
@endif
-
-
-
-Token
-
-Public Key
-@if( Session::has("admin"))
-Delete
-@endif
-
-
-@foreach( $tokens as $token => $publicKey)
-
-
-{{ $token }}
-
-
-{{ $publicKey }}
-
-@if( Session::has("admin"))
-
-
-
-@endif
-
+
+
+@foreach ($tokens as $val)
+
+
+
+@if($val->description!=null)
+{{{ $val->description
}}}
+@else
+NO
DESCRIPTION!
+@endif
+
+
+
+
+
+
+
+
+Copy
+
+
+
+
+
+description=="Default SSH Key") disabled @endif>Delete
Review comment:
Likewise, don't need to do anything special with "Default SSH Key".
This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
> Gateway credential store UI also to have the same format as individual user
> settings
>
>
> Key: AIRAVATA-2279
> URL: https://issues.apache.org/jira/browse/AIRAVATA-2279
> Project: Airavata
> Issue Type: Bug
> Components: PGA PHP Web Gateway
> Environment: dev.seagrid.org
>Reporter: Eroma
>Assignee: Marcus Christie
>Priority: Major
> Fix For: 0.18
>
>
> Currently there are no description ora copy button to copy the public key in
> gateway credential store.
> Unifying the UI with User settings will make it easy for the gateway admins.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (AIRAVATA-2279) Gateway credential store UI also to have the same format as individual user settings
[
https://issues.apache.org/jira/browse/AIRAVATA-2279?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16238406#comment-16238406
]
ASF GitHub Bot commented on AIRAVATA-2279:
--
machristie commented on a change in pull request #75: [AIRAVATA-2279 & 2280]
FIXED.
URL:
https://github.com/apache/airavata-php-gateway/pull/75#discussion_r148894236
##
File path: app/controllers/AdminController.php
##
@@ -345,9 +345,22 @@ public function deleteRole(){
public function credentialStoreView(){
Session::put("admin-nav", "credential-store");
-$tokens = AdminUtilities::get_all_ssh_tokens();
+$tokens = AdminUtilities::get_all_ssh_tokens_with_description();
+//Auto-generating the Default SSH Key if there is no key with such
description.
Review comment:
We don't need to generate a "Default SSH Key".
This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
> Gateway credential store UI also to have the same format as individual user
> settings
>
>
> Key: AIRAVATA-2279
> URL: https://issues.apache.org/jira/browse/AIRAVATA-2279
> Project: Airavata
> Issue Type: Bug
> Components: PGA PHP Web Gateway
> Environment: dev.seagrid.org
>Reporter: Eroma
>Assignee: Marcus Christie
>Priority: Major
> Fix For: 0.18
>
>
> Currently there are no description ora copy button to copy the public key in
> gateway credential store.
> Unifying the UI with User settings will make it easy for the gateway admins.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (AIRAVATA-2444) In Users, should have users first name, last name and email listed as well.
[ https://issues.apache.org/jira/browse/AIRAVATA-2444?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16238381#comment-16238381 ] Marcus Christie commented on AIRAVATA-2444: --- I'm merged (via cherry-pick) these commits to master. I'll deploy them to production on Monday. > In Users, should have users first name, last name and email listed as well. > --- > > Key: AIRAVATA-2444 > URL: https://issues.apache.org/jira/browse/AIRAVATA-2444 > Project: Airavata > Issue Type: Improvement > Components: PGA PHP Web Gateway >Affects Versions: 0.17 > Environment: http://149.165.156.11/ >Reporter: Eroma >Assignee: Stephen Paul Adithela >Priority: Minor > Fix For: 0.19 > > > Currently only the username is listed. Listing above makes search and > locating user accounts easy. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (AIRAVATA-2444) In Users, should have users first name, last name and email listed as well.
[ https://issues.apache.org/jira/browse/AIRAVATA-2444?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16238378#comment-16238378 ] ASF subversion and git services commented on AIRAVATA-2444: --- Commit 4f5aff994fce8537dfa4f4f0e03685c5a6fdd396 in airavata-php-gateway's branch refs/heads/master from [~marcuschristie] [ https://gitbox.apache.org/repos/asf?p=airavata-php-gateway.git;h=4f5aff9 ] AIRAVATA-2444 Fix searchUsers to return user fields > In Users, should have users first name, last name and email listed as well. > --- > > Key: AIRAVATA-2444 > URL: https://issues.apache.org/jira/browse/AIRAVATA-2444 > Project: Airavata > Issue Type: Improvement > Components: PGA PHP Web Gateway >Affects Versions: 0.17 > Environment: http://149.165.156.11/ >Reporter: Eroma >Assignee: Stephen Paul Adithela >Priority: Minor > Fix For: 0.19 > > > Currently only the username is listed. Listing above makes search and > locating user accounts easy. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (AIRAVATA-2582) CILogon: support direct redirects to institutional logins
[
https://issues.apache.org/jira/browse/AIRAVATA-2582?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16238342#comment-16238342
]
Marcus Christie commented on AIRAVATA-2582:
---
Some information from Terry Fleury:
{quote}
Hi Marcus,
I'm glad to hear that CILogon is working for you.
It is possible to redirect to a specific IdP using a specialized skin.
However, there is a reason that the CILogon Identity Provider page is
displayed to the user: the page acts as the Attribute Release Consent
screen which lets the user know what attributes will be released to your
portal.
You may have seen text at the top of the CILogon page similar to the
following:
"Example Portal" requests access to the following information. If you do
not approve this request, do not proceed.
* Your CILogon username
* Your name
* Your email address
* Your username and affiliation from your identity provider
* A certificate that allows "Example Portal" to act on your behalf
(Note that the number of bullet points will vary depending on the scopes
requested by your OAuth2 client.)
In order to bypass this Consent page, CILogon staff will need to verify
that your Portal site displays similar information to the user before
redirection to the IU Identity Provider. Then we can add your portal's
callback uri(s) to a whitelist for the 'bypass' skin.
We had previously created a skin named 'iugateway' which automatically
redirected to the IU IdP. The two portals currently whitelisted to use
the 'iugateway' skin are:
https://cybergateway.uits.iu.edu/
https://iub.globusonline.org/
We can add other portals / callback uris if they show an Attribute
Release Consent screen to the user.
Hope that helps.
-Terry
{quote}
> CILogon: support direct redirects to institutional logins
> -
>
> Key: AIRAVATA-2582
> URL: https://issues.apache.org/jira/browse/AIRAVATA-2582
> Project: Airavata
> Issue Type: Bug
>Reporter: Marcus Christie
>Assignee: Marcus Christie
>Priority: Major
>
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (AIRAVATA-2581) Manually deploy Django version of dev seagrid
[
https://issues.apache.org/jira/browse/AIRAVATA-2581?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16238309#comment-16238309
]
Marcus Christie commented on AIRAVATA-2581:
---
Current work I've done so far
{noformat}
[Using Daemon process with
mod_wsgi](https://modwsgi.readthedocs.io/en/develop/user-guides/quick-configuration-guide.html#delegation-to-daemon-process)
* also has an example virtual host configuration
Steps:
* checkout the django code
* create a virtual environment
* source virtual env and run `pip install -r requirements.txt` in that
environment
* create a settings_local.py will have all the necessary settings
* set the STATIC_ROOT in settings_local.py
* run build_js.sh
* run `collectstatic`
* create virtual host config [like this
example](https://modwsgi.readthedocs.io/en/develop/user-guides/quick-configuration-guide.html#delegation-to-daemon-process)
* gracefully restart apache
* create a database in MySQL for django database
* migrate database and configure
For the test server:
* connect to dev.seagrid.org like we currently have
* domain name: django.seagrid.org
Do we need to rebuild mod_wsgi every time that the python version is updated?
* No. Python3.4 installed by yum was compiled with `--enable-shared`. See
[python patch level
mismatch](https://modwsgi.readthedocs.io/en/develop/user-guides/installation-issues.html#python-patch-level-mismatch)
* verifying
```
[centos@pga-scigap-develop ~]$ python3
Python 3.4.5 (default, May 29 2017, 15:17:55)
[GCC 4.8.5 20150623 (Red Hat 4.8.5-11)] on linux
Type "help", "copyright", "credits" or "license" for more information.
>>> import sysconfig
>>> sysconfig.get_config_var('CONFIG_ARGS')
"'--build=x86_64-redhat-linux-gnu' '--host=x86_64-redhat-linux-gnu'
'--program-prefix=' '--disable-dependency-tracking' '--prefix=/usr'
'--exec-prefix=/usr' '--bindir=/usr/bin' '--sbindir=/usr/sbin'
'--sysconfdir=/etc' '--datadir=/usr/share' '--includedir=/usr/include'
'--libdir=/usr/lib64' '--libexecdir=/usr/libexec' '--localstatedir=/var'
'--sharedstatedir=/var/lib' '--mandir=/usr/share/man'
'--infodir=/usr/share/info' '--enable-ipv6' '--enable-shared'
'--with-computed-gotos=yes' '--with-dbmliborder=gdbm:ndbm:bdb'
'--with-system-expat' '--with-system-ffi' '--enable-loadable-sqlite-extensions'
'--with-systemtap' '--with-valgrind' '--without-ensurepip'
'build_alias=x86_64-redhat-linux-gnu' 'host_alias=x86_64-redhat-linux-gnu'
'CFLAGS=-O2 -g -pipe -Wall -Wp,-D_FORTIFY_SOURCE=2 -fexceptions
-fstack-protector-strong --param=ssp-buffer-size=4 -grecord-gcc-switches -m64
-mtune=generic -D_GNU_SOURCE -fPIC -fwrapv ' 'LDFLAGS=-Wl,-z,relro '
'CPPFLAGS= ' 'PKG_CONFIG_PATH=:/usr/lib64/pkgconfig:/usr/share/pkgconfig'"
```
Actual installation
* sudo yum -y install python34
* sudo yum -y install httpd-devel
* sudo yum -y install python34-devel
* install mod_wsgi from source
```
mkdir mod_wsgi
cd mod_wsgi/
curl -LO https://github.com/GrahamDumpleton/mod_wsgi/archive/4.5.17.tar.gz
tar zxf 4.5.17.tar.gz
cd mod_wsgi-4.5.17/
./configure --with-python=/usr/bin/python3
make
sudo make install
```
* configure Apache to load mod_wsgi
```
sudo vim /etc/httpd/conf.modules.d/00-wsgi.conf
```
* 00-wsgi.conf file contains
```
LoadModule wsgi_module modules/mod_wsgi.so
```
* `sudo apachectl restart`
* Verify line in apache error log showing the mod_wsgi and Python34 loaded:
```
[Thu Aug 24 14:20:20.171560 2017] [mpm_prefork:notice] [pid 6657] AH00163:
Apache/2.4.6 (CentOS) OpenSSL/1.0.1e-fips mod_wsgi/4.5.17 Python/3.4 PHP/5.4.16
configured -- resuming normal operations
```
* Clean up build: `make clean`
* Clone django code and setup virtual environment
```
mkdir django-seagrid
cd django-seagrid/
git clone https://github.com/machristie/django-airavata-gateway.git
python3 -m venv venv
source venv/bin/activate
cd django-airavata-gateway/
pip install -r requirements.txt
```
* create the settings_local.py file
"""
Override default Django settings for a particular instance.
Copy this file to settings_local.py and modify as appropriate. This file
will
be imported into settings.py last of all so settings in this file override
any
defaults specified in settings.py.
"""
import os
# Build paths inside the project like this: os.path.join(BASE_DIR, ...)
BASE_DIR = os.path.dirname(os.path.dirname(os.path.abspath(__file__)))
# Keycloak Configuration
KEYCLOAK_CLIENT_ID = 'pga'
KEYCLOAK_CLIENT_SECRET = '5d2dc66a-f54e-4fa9-b78f-80d33aa862c1'
KEYCLOAK_AUTHORIZE_URL =
'https://iamdev.scigap.org/auth/realms/seagrid/protocol/openid-connect/auth'
KEYCLOAK_TOKEN_URL =
'https://iamdev.scigap.org/auth/realms/seagrid/protocol/openid-connect/token'
KEYCLOAK_USERINFO_URL =
'https://iamdev.scigap.org/auth/realms/seagrid/protocol/openid-connect/userinfo'
KEYCLOAK_LOGOUT_URL =
[jira] [Created] (AIRAVATA-2581) Manually deploy Django version of dev seagrid
Marcus Christie created AIRAVATA-2581: - Summary: Manually deploy Django version of dev seagrid Key: AIRAVATA-2581 URL: https://issues.apache.org/jira/browse/AIRAVATA-2581 Project: Airavata Issue Type: Sub-task Reporter: Marcus Christie Assignee: Marcus Christie Priority: Major -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (AIRAVATA-2580) Django: automate deployment
Marcus Christie created AIRAVATA-2580: - Summary: Django: automate deployment Key: AIRAVATA-2580 URL: https://issues.apache.org/jira/browse/AIRAVATA-2580 Project: Airavata Issue Type: Bug Reporter: Marcus Christie Assignee: Marcus Christie Priority: Major -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Closed] (AIRAVATA-2466) In Edit experiment mode max, CPU, node and walltime are not displayed.
[ https://issues.apache.org/jira/browse/AIRAVATA-2466?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Marcus Christie closed AIRAVATA-2466. - Resolution: Fixed > In Edit experiment mode max, CPU, node and walltime are not displayed. > -- > > Key: AIRAVATA-2466 > URL: https://issues.apache.org/jira/browse/AIRAVATA-2466 > Project: Airavata > Issue Type: Bug > Components: PGA PHP Web Gateway >Affects Versions: 0.17 > Environment: https://dev.seagrid.org >Reporter: Eroma >Assignee: Marcus Christie >Priority: Major > Fix For: 0.19 > > -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (AIRAVATA-2090) Dockerize Airavata
[ https://issues.apache.org/jira/browse/AIRAVATA-2090?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16237216#comment-16237216 ] ASF GitHub Bot commented on AIRAVATA-2090: -- jeffreypeter commented on a change in pull request #127: Added Docker files for [AIRAVATA-2090] URL: https://github.com/apache/airavata/pull/127#discussion_r148721070 ## File path: dev-tools/docker/apiserver/airavata-server.properties ## @@ -0,0 +1,358 @@ +# +# +# Licensed to the Apache Software Foundation (ASF) under one +# or more contributor license agreements. See the NOTICE file +# distributed with this work for additional information +# regarding copyright ownership. The ASF licenses this file +# to you under the Apache License, Version 2.0 (the +# "License"); you may not use this file except in compliance +# with the License. You may obtain a copy of the License at +# +# http://www.apache.org/licenses/LICENSE-2.0 +# +# Unless required by applicable law or agreed to in writing, +# software distributed under the License is distributed on an +# "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY +# KIND, either express or implied. See the License for the +# specific language governing permissions and limitations +# under the License. +# + +### +# +# This properties file provides configuration for all Airavata Services: +# API Server, Registry, Workflow Interpreter, GFac, Orchestrator +# +### + +### +# API Server Registry Configuration +### + +#for derby [AiravataJPARegistry] +registry.jdbc.driver=org.apache.derby.jdbc.ClientDriver +registry.jdbc.url=jdbc:derby:experiment_catalog;create=true;user=airavata;password=airavata +# MariaDB database configuration +#registry.jdbc.driver=org.mariadb.jdbc.Driver +#registry.jdbc.url=jdbc:mariadb://localhost:3306/experiment_catalog +registry.jdbc.user=airavata +registry.jdbc.password=airavata +#FIXME: Probably the following property should be removed. +start.derby.server.mode=false +validationQuery=SELECT 1 from CONFIGURATION +cache.enable=true +jpa.cache.size=5000 +#jpa.connection.properties=MaxActive=10,MaxIdle=5,MinIdle=2,MaxWait=6,testWhileIdle=true,testOnBorrow=true +enable.sharing=true + +# Properties for default user mode +default.registry.user=admin +default.registry.password=admin +default.registry.password.hash.method=SHA +default.registry.gateway=php_reference_gateway +super.tenant.gatewayId=php_reference_gateway + +# Properties for cluster status monitoring +# cluster status monitoring job repeat time in seconds +cluster.status.monitoring.enable=false +cluster.status.monitoring.repeat.time=18000 + +### +# Application Catalog DB Configuration +### +#for derby [AiravataJPARegistry] +appcatalog.jdbc.driver=org.apache.derby.jdbc.ClientDriver +appcatalog.jdbc.url=jdbc:derby:app_catalog;create=true;user=airavata;password=airavata +# MariaDB database configuration +#appcatalog.jdbc.driver=org.mariadb.jdbc.Driver +#appcatalog.jdbc.url=jdbc:mariadb://localhost:3306/app_catalog +appcatalog.jdbc.user=airavata +appcatalog.jdbc.password=airavata +appcatalog.validationQuery=SELECT 1 from CONFIGURATION + +## +# Replica Catalog DB Configuration +### +#for derby [AiravataJPARegistry] +replicacatalog.jdbc.driver=org.apache.derby.jdbc.ClientDriver +replicacatalog.jdbc.url=jdbc:derby:replica_catalog;create=true;user=airavata;password=airavata +# MariaDB database configuration +#replicacatalog.jdbc.driver=org.mariadb.jdbc.Driver +#replicacatalog.jdbc.url=jdbc:mariadb://localhost:3306/replica_catalog +replicacatalog.jdbc.user=airavata +replicacatalog.jdbc.password=airavata +replicacatalog.validationQuery=SELECT 1 from CONFIGURATION + +### +# Workflow Catalog DB Configuration +### +#for derby [AiravataJPARegistry] +workflowcatalog.jdbc.driver=org.apache.derby.jdbc.ClientDriver +workflowcatalog.jdbc.url=jdbc:derby:workflow_catalog;create=true;user=airavata;password=airavata +# MariaDB database configuration +#workflowcatalog.jdbc.driver=org.mariadb.jdbc.Driver +#workflowcatalog.jdbc.url=jdbc:mariadb://localhost:3306/workflow_catalog +workflowcatalog.jdbc.user=airavata +workflowcatalog.jdbc.password=airavata +workflowcatalog.validationQuery=SELECT 1 from CONFIGURATION +
