[
https://issues.apache.org/jira/browse/DLAB-653?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vira Vitanska updated DLAB-653:
-------------------------------
Description:
As a User I want to create analytical tools so that I can use and manage them
for analytical calculations.
*Preconditions:*
# User is logged-in DLab
# User is located in ‘List of Resources’ page
*Description:*
If User clicks ‘+ Create new’ button ‘Analytical tool’ popup appears which
consists of:
* ‘Select template’ - drop down list
* ‘Name’ - textbox it should be unique within endpoint and user
* ‘Instance shape’ (AWS)/‘Virtual machine size’ (Azure) drop down list
* ‘Project’ - drop down list
* ‘Endpoint’ - drop down list
* two buttons ‘Cancel’ and ‘Create’
All fields are mandatory.
If User clicks ‘Create’ button the analytical tool is creating and ‘Analytical
tool’ popup is closed.
If User clicks ‘Cancel’ button the analytical tool is not created and
‘Analytical tool’ popup is closed.
*Acceptance criteria:*
# User is able to create analytical tool
# User is able to choose in what project analytical tool will be created
# During the first notebook template creation shared AMI is created. Shared
AMI is per Endpoint and per Cloud
# User can create notebook from custom AMI. Custom AMI is per user and per
Cloud
# It is not allowed for other user to access to notebooks within same project
on identity provider level - [(v1) - SHORT TERM]
# Users works under his own identity. All actions are logged from that
username *[(v2) - LONG TERM]*
was:
As a User I want to create analytical tools so that I can use and manage them
for analytical calculations.
*Preconditions:*
# User is logged-in DLab
# User is located in ‘List of Resources’ page
*Description:*
If User clicks ‘+ Create new’ button ‘Analytical tool’ popup appears which
consists of:
* ‘Select template’ - drop down list
* ‘Name’ - textbox it should be unique within endpoint and user
* ‘Instance shape’ (AWS)/‘Virtual machine size’ (Azure) drop down list
* ‘Project’ - drop down list
* ‘Endpoint’ - drop down list
* two buttons ‘Cancel’ and ‘Create’
All fields are mandatory.
If User clicks ‘Create’ button the analytical tool is creating and ‘Analytical
tool’ popup is closed.
If User clicks ‘Cancel’ button the analytical tool is not created and
‘Analytical tool’ popup is closed.
*Acceptance criteria:*
# User is able to create analytical tool
# User is able to choose in what project analytical tool will be created
# During the first notebook template creation shared AMI is created. Shared
AMI is per Endpoint and per Cloud
# User can create notebook from custom AMI. Custom AMI is per user and per
Cloud
# It is not allowed for other user to access to notebooks within same project
on identity provider level - [(v1) - SHORT TERM]
# Users works under his own identity. All actions are logged from that
username [(v2) - LONG TERM]
> Possibility to create analytical tool
> -------------------------------------
>
> Key: DLAB-653
> URL: https://issues.apache.org/jira/browse/DLAB-653
> Project: Apache DLab
> Issue Type: Task
> Components: GCP
> Reporter: Vira Vitanska
> Assignee: Vira Vitanska
> Priority: Major
> Labels: Debian, Project
> Fix For: v.2.2
>
>
> As a User I want to create analytical tools so that I can use and manage them
> for analytical calculations.
>
> *Preconditions:*
> # User is logged-in DLab
> # User is located in ‘List of Resources’ page
>
> *Description:*
> If User clicks ‘+ Create new’ button ‘Analytical tool’ popup appears which
> consists of:
> * ‘Select template’ - drop down list
> * ‘Name’ - textbox it should be unique within endpoint and user
> * ‘Instance shape’ (AWS)/‘Virtual machine size’ (Azure) drop down list
> * ‘Project’ - drop down list
> * ‘Endpoint’ - drop down list
> * two buttons ‘Cancel’ and ‘Create’
> All fields are mandatory.
> If User clicks ‘Create’ button the analytical tool is creating and
> ‘Analytical tool’ popup is closed.
> If User clicks ‘Cancel’ button the analytical tool is not created and
> ‘Analytical tool’ popup is closed.
>
> *Acceptance criteria:*
> # User is able to create analytical tool
> # User is able to choose in what project analytical tool will be created
> # During the first notebook template creation shared AMI is created. Shared
> AMI is per Endpoint and per Cloud
> # User can create notebook from custom AMI. Custom AMI is per user and per
> Cloud
> # It is not allowed for other user to access to notebooks within same
> project on identity provider level - [(v1) - SHORT TERM]
> # Users works under his own identity. All actions are logged from that
> username *[(v2) - LONG TERM]*
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
