[ 
https://issues.apache.org/jira/browse/DATALAB-2314?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Vira Vitanska updated DATALAB-2314:
-----------------------------------
    Description: 
# There is only a billing and a provisioning services for external endpoint. 
So, should we show self-service for external endpoint? (i) {color:#de350b}No, 
we should not show them{color}
 # Provisioning/billing services restart does not work. Error 404
 # Provisioning/billing.yml editing does not work. Error 400
 # In DataLab Web UI provisioning/billing.yml for external endpoint show not 
external endpoint values. They show values local endpoint
 # If choose active external endpoint in Select endpoint drop down list the 404 
error appears
 # If self-service is not needed for external endpoint do not do point6. If 
restart a self-service message appears : 
{code:java}
Success!
Service restarting started!
{code}
However in Network 404 error appears

 #  
If self-service is not needed for external endpoint do not do point7. If 
edit/save a self-service. yml a message appears : 
{code:java}
Success!
Service configuration saved!
{code}
However in Network 404 error appears

  was:
# There is only a billing and a provisioning services for external endpoint. 
So, should we show self-service for external endpoint?
 # Provisioning/billing services restart does not work. Error 404
 # Provisioning/billing.yml editing does not work. Error 400
 # In DataLab Web UI provisioning/billing.yml for external endpoint show not 
external endpoint values. They show values local endpoint
 # If choose active external endpoint in Select endpoint drop down list the 404 
error appears
 # If self-service is not needed for external endpoint do not do point6. If 
restart a self-service message appears : 
{code:java}
Success!
Service restarting started!
{code}
However in Network 404 error appears

 # If self-service is not needed for external endpoint do not do point7. If 
edit/save a self-service. yml a message appears : 
{code:java}
Success!
Service configuration saved!
{code}
However in Network 404 error appears


> [Configuration]: Set of task for external endpoint for provisioning/billing 
> services
> ------------------------------------------------------------------------------------
>
>                 Key: DATALAB-2314
>                 URL: https://issues.apache.org/jira/browse/DATALAB-2314
>             Project: Apache DataLab
>          Issue Type: Task
>      Security Level: Public(Regular Issues) 
>          Components: DataLab Main
>            Reporter: Vira Vitanska
>            Assignee: Yurii Kinash
>            Priority: Major
>              Labels: AWS, AZURE, Back-end, Debian, GCP, RedHat
>             Fix For: v.2.5
>
>         Attachments: P6 - Self-service.png, P7 - Selfe-service.png, Point2 - 
> Provisioning-billing restarting.png, Point3 - Provisioning-billing 
> editing.png, Pont5 - endpoint drop down list.png
>
>
> # There is only a billing and a provisioning services for external endpoint. 
> So, should we show self-service for external endpoint? (i) {color:#de350b}No, 
> we should not show them{color}
>  # Provisioning/billing services restart does not work. Error 404
>  # Provisioning/billing.yml editing does not work. Error 400
>  # In DataLab Web UI provisioning/billing.yml for external endpoint show not 
> external endpoint values. They show values local endpoint
>  # If choose active external endpoint in Select endpoint drop down list the 
> 404 error appears
>  # If self-service is not needed for external endpoint do not do point6. If 
> restart a self-service message appears : 
> {code:java}
> Success!
> Service restarting started!
> {code}
> However in Network 404 error appears
>  #  
> If self-service is not needed for external endpoint do not do point7. If 
> edit/save a self-service. yml a message appears : 
> {code:java}
> Success!
> Service configuration saved!
> {code}
> However in Network 404 error appears



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to