Re: Podling Report Reminder - March 2019

[Konstantin Boudnik]

And done. Thanks Henry!
--
  With regards,
Konstantin (Cos) Boudnik
2CAC 8312 4870 D885 8616  6115 220F 6980 1F27 E622

Disclaimer: Opinions expressed in this email are those of the author,
and do not necessarily represent the views of any company the author
might be affiliated with at the moment of writing.

On Mon, Mar 11, 2019 at 2:57 AM Henry Saputra  wrote:
>
> I have uploaded the report to Wiki abd have signed it. Cos, could you help
> revise as needed and sign it?
>
> Thanks,
> Henry
>
> On Tue, Mar 5, 2019, 12:29 AM Dmytro Liaskovskyi
>  wrote:
>
> > Thanks Cos,
> > I fixed this in-line __
> >
> > DMYTRO LIASKOVSKYI
> > Software Engineering Manager
> >
> > Office: +380 322 424 642 x 57729 
> >  Cell: +380 97 341 1315Email:
> > dmytro_liaskovs...@epam.com
> > Lviv, Ukraine   epam.com 
> >
> > CONFIDENTIALITY CAUTION AND DISCLAIMER
> > This message is intended only for the use of the individual(s) or
> > entity(ies) to which it is addressed and contains information that is
> > legally privileged and confidential. If you are not the intended recipient,
> > or the person responsible for delivering the message to the intended
> > recipient, you are hereby notified that any dissemination, distribution or
> > copying of this communication is strictly prohibited. All unintended
> > recipients are obliged to delete this message and destroy any printed
> > copies.
> >
> > On 3/4/19, 19:24, "Konstantin Boudnik"  wrote:
> >
> > Thanks Dmytro!
> >
> > +1
> >
> > I suggest to change "we've been working hardly towards" to "we've been
> > working hard towards...". Otherwise, it sounds like the community
> > wasn't doing much to make the release happen...
> >
> > Thanks!
> > --
> >   With regards,
> > Konstantin (Cos) Boudnik
> > 2CAC 8312 4870 D885 8616  6115 220F 6980 1F27 E622
> >
> > Disclaimer: Opinions expressed in this email are those of the author,
> > and do not necessarily represent the views of any company the author
> > might be affiliated with at the moment of writing.
> >
> >
> > On Mon, Mar 4, 2019 at 3:44 PM Dmytro Liaskovskyi
> >  wrote:
> > >
> > > *   Your project name
> > >
> > > DLab
> > >
> > > *   A brief description of your project, which assumes no
> > knowledge of the project or necessarily of its field
> > >
> > > DLab is a platform for creating self-service, exploratory data
> > science environments in the cloud using best-of-breed data science tools.
> > >
> > > *   A list of the three most important issues to address in the
> > move towards graduation.
> > >
> > >   1. Exectute the SGA between EPAM and the ASF so code can be
> > imported - done
> > >   2. Complete on-boarding of initial committers - done
> > >   3. Work toward an initial Apache release - release branch created.
> > Pending VOTE apache general list
> > >
> > > *   Any issues that the Incubator PMC or ASF Board might
> > wish/need to be aware of
> > >
> > > Not this time
> > >
> > > *   How has the community developed since the last report
> > >
> > > All initial committers have completed on-boarding. Also we've added
> > 3 more contributors: Anna Orlovska, Oleksandr Isniuk and Demyan Mysakovets
> > who are currently onboarding and doing initial work to prove contribution.
> > >
> > > *   How has the project developed since the last report.
> > >
> > > The team fully switched our work to Apache Infrastructure: JIRA,
> > Git. Also the team has been working hard towards first Apache release.
> > Release branch has been created and is waiting for further acceptance by
> > means of voting in apache general mailing list. We've already reviewed and
> > fixed couple of enhancements proposed by our mentors in regards to the
> > release.
> > > We've added bunch of new features, all of them described in release
> > notes: https://github.com/apache/incubator-dlab/releases/tag/2.1
> > >
> > > *   How does the podling rate their own maturity.
> > >
> > >   [] Initial setup
> > >   [X] Working towards first release
> > >   [X] Community building
> > >   [ ] Nearing graduation
> > >   [ ] Other:
> > >
> > > *   Help needed by DLab team from Apache:
> > >
> > > We would highly appreciate if following page could start being
> > populated: https://incubator.apache.org/projects/dlab.html, currently
> > there are many empty pages, not all sections are filled in.
> > > The team can provide all needed information, but unfortunately we
> > don't ability to Edit this page.
> > >
> > > This should be appended to the Incubator Wiki page at:
> > > https://wiki.apache.org/incubator/March2019
> > >
> > > DMYTRO LIASKOVSKYI
> > > Software Engineering Manager
> > >
> > > Office: +380 322 424 642 x 57729
> >Cell: +380 97 341 1315
> >Em

Re: [MENTORS] Release support

[Henry Saputra]

LGTM.

Could you kickoff another VOTE thread for v2.1 RC 1 then?

Thanks,

- Henry

On Fri, Mar 8, 2019 at 1:20 AM Bohdan Hliva 
wrote:

> Hi Henry,
>
> Changes are in v2.1 branch
> https://github.com/apache/incubator-dlab/tree/v2.1
>
>
>
>
> BOHDAN HLIVA
> Lead Software Engineer
>
> Office: +380 322 424 642 x 42572   Cell: +380 63 151 2201   Email:
> bohdan_hl...@epam.com
> Lviv, Ukraine   epam.com
>
> CONFIDENTIALITY CAUTION AND DISCLAIMER
> This message is intended only for the use of the individual(s) or
> entity(ies) to which it is addressed and contains information that is
> legally privileged and confidential. If you are not the intended recipient,
> or the person responsible for delivering the message to the intended
> recipient, you are hereby notified that any dissemination, distribution or
> copying of this communication is strictly prohibited. All unintended
> recipients are obliged to delete this message and destroy any printed
> copies.
>
>
> On Mar 7, 2019, at 21:56, Henry Saputra  henry.sapu...@gmail.com>> wrote:
>
> Sorry I missed this email due to massive JIRA update emails.
>
> Has the changes committed to master branch?
>
> - Henry
>
> On Thu, Feb 28, 2019 at 5:13 AM Bohdan Hliva  >
> wrote:
>
> Dear mentors,
>
> I have some questions regarding release:
> 1. Release headers:
>
>  *   All headers are updated as described here
> http://www.apache.org/legal/src-headers.html;
>  *   There are some files in source code that does not support comments:
> e.g. .json, .txt, .ipynb, some config files etc. How to be with such files?
>
> 2. Notice and License files are also updated. Could you please check
> whether it correct or not?
> 3. There also was a note regarding provenance of picture that we use for
> test purpose. Should we include some link of source from which it was
> downloaded?
> 4. Compiled code exists in source release. Should we store it somewhere
> separately?
>
> Thanks in advance!
>
>
>

[jira] [Commented] (DLAB-328) [Tech debt]: Refactor a code for appropriate Apache Toree kernel configuring for Jupyter notebook

[Vira Vitanska (JIRA)]

[ 
https://issues.apache.org/jira/browse/DLAB-328?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16790802#comment-16790802
 ] 

Vira Vitanska commented on DLAB-328:


Data Engine creation fails:

!DataProc.PNG!

> [Tech debt]: Refactor a code for appropriate Apache Toree kernel configuring 
> for Jupyter notebook
> -
>
> Key: DLAB-328
> URL: https://issues.apache.org/jira/browse/DLAB-328
> Project: Apache DLab
>  Issue Type: Task
>  Components: AWS, Azure, GCP
>Reporter: Vira Vitanska
>Assignee: Demyan Mysakovets
>Priority: Major
>  Labels: Debian, DevOps, RedHat
> Fix For: v.2.2
>
> Attachments: DataProc.PNG, Jupyter.PNG, 
> failed_data_prep_Scala_with_Toree.png
>
>
> 1. Delete toree from sources:
> 1.1./infrastructure-provisioning/src/general/files/os/toree_kernel.tar.gz
> 1.2./infrastructure-provisioning/src/general/files/os/toree-assembly-0.2.0.jar
>  
> 2. Use toree from public repository
>  
>  
>  



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

-
To unsubscribe, e-mail: dev-unsubscr...@dlab.apache.org
For additional commands, e-mail: dev-h...@dlab.apache.org

[jira] [Updated] (DLAB-328) [Tech debt]: Refactor a code for appropriate Apache Toree kernel configuring for Jupyter notebook

[Vira Vitanska (JIRA)]

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

Vira Vitanska updated DLAB-328:
---
Attachment: DataProc.PNG

> [Tech debt]: Refactor a code for appropriate Apache Toree kernel configuring 
> for Jupyter notebook
> -
>
> Key: DLAB-328
> URL: https://issues.apache.org/jira/browse/DLAB-328
> Project: Apache DLab
>  Issue Type: Task
>  Components: AWS, Azure, GCP
>Reporter: Vira Vitanska
>Assignee: Demyan Mysakovets
>Priority: Major
>  Labels: Debian, DevOps, RedHat
> Fix For: v.2.2
>
> Attachments: DataProc.PNG, Jupyter.PNG, 
> failed_data_prep_Scala_with_Toree.png
>
>
> 1. Delete toree from sources:
> 1.1./infrastructure-provisioning/src/general/files/os/toree_kernel.tar.gz
> 1.2./infrastructure-provisioning/src/general/files/os/toree-assembly-0.2.0.jar
>  
> 2. Use toree from public repository
>  
>  
>  



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

-
To unsubscribe, e-mail: dev-unsubscr...@dlab.apache.org
For additional commands, e-mail: dev-h...@dlab.apache.org

[jira] [Updated] (DLAB-328) [Tech debt]: Refactor a code for appropriate Apache Toree kernel configuring for Jupyter notebook

[Anna Orlovska (JIRA)]

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

Anna Orlovska updated DLAB-328:
---
Attachment: failed_data_prep_Scala_with_Toree.png

> [Tech debt]: Refactor a code for appropriate Apache Toree kernel configuring 
> for Jupyter notebook
> -
>
> Key: DLAB-328
> URL: https://issues.apache.org/jira/browse/DLAB-328
> Project: Apache DLab
>  Issue Type: Task
>  Components: AWS, Azure, GCP
>Reporter: Vira Vitanska
>Assignee: Demyan Mysakovets
>Priority: Major
>  Labels: Debian, DevOps, RedHat
> Fix For: v.2.2
>
> Attachments: Jupyter.PNG, failed_data_prep_Scala_with_Toree.png
>
>
> 1. Delete toree from sources:
> 1.1./infrastructure-provisioning/src/general/files/os/toree_kernel.tar.gz
> 1.2./infrastructure-provisioning/src/general/files/os/toree-assembly-0.2.0.jar
>  
> 2. Use toree from public repository
>  
>  
>  



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

-
To unsubscribe, e-mail: dev-unsubscr...@dlab.apache.org
For additional commands, e-mail: dev-h...@dlab.apache.org

[jira] [Commented] (DLAB-328) [Tech debt]: Refactor a code for appropriate Apache Toree kernel configuring for Jupyter notebook

[Anna Orlovska (JIRA)]

[ 
https://issues.apache.org/jira/browse/DLAB-328?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16790675#comment-16790675
 ] 

Anna Orlovska commented on DLAB-328:


"Flights_data_Preparation_Scala-Spark.ipynb" fails with Apache Toree kernel on 
Jupyter notebook. !failed_data_prep_Scala_with_Toree.png!
 
 

> [Tech debt]: Refactor a code for appropriate Apache Toree kernel configuring 
> for Jupyter notebook
> -
>
> Key: DLAB-328
> URL: https://issues.apache.org/jira/browse/DLAB-328
> Project: Apache DLab
>  Issue Type: Task
>  Components: AWS, Azure, GCP
>Reporter: Vira Vitanska
>Assignee: Demyan Mysakovets
>Priority: Major
>  Labels: Debian, DevOps, RedHat
> Fix For: v.2.2
>
> Attachments: Jupyter.PNG, failed_data_prep_Scala_with_Toree.png
>
>
> 1. Delete toree from sources:
> 1.1./infrastructure-provisioning/src/general/files/os/toree_kernel.tar.gz
> 1.2./infrastructure-provisioning/src/general/files/os/toree-assembly-0.2.0.jar
>  
> 2. Use toree from public repository
>  
>  
>  



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

-
To unsubscribe, e-mail: dev-unsubscr...@dlab.apache.org
For additional commands, e-mail: dev-h...@dlab.apache.org

[jira] [Commented] (DLAB-473) 'Caffe' doesn’t run successfully on Deep Learning

[Vira Vitanska (JIRA)]

[ 
https://issues.apache.org/jira/browse/DLAB-473?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16790670#comment-16790670
 ] 

Vira Vitanska commented on DLAB-473:


Caffe runs successfully on *RedHat* on AWS

> 'Caffe' doesn’t run successfully on Deep Learning
> -
>
> Key: DLAB-473
> URL: https://issues.apache.org/jira/browse/DLAB-473
> Project: Apache DLab
>  Issue Type: Bug
>  Components: AWS, Azure, GCP
>Reporter: Anna Orlovska
>Assignee: Oleksandr Isniuk
>Priority: Major
>  Labels: Debian, DevOps, GCP_demo
> Fix For: v.2.2
>
> Attachments: failed_data_viz_Caffe_on_DeLer.png
>
>
> *Preconditions:*
>  Deep Learning is created and running.
> *Steps to reproduce:*
>  1. Open notebook URL in browser.
> 2. Upload file “Caffe.ipynb”.
> 3. Choose Local PySpark (Python-2.7 / Spark-2.3.2 ) kernel.
> 4. Run playbook.
> *Expected result:*
>  Playbook is run successfully. 
> *Actual result:*
>  Playbook doesn’t run successfully.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

-
To unsubscribe, e-mail: dev-unsubscr...@dlab.apache.org
For additional commands, e-mail: dev-h...@dlab.apache.org

[jira] [Updated] (DLAB-523) [GCP][DeepLearning]: Data Engine creation fails

[Vira Vitanska (JIRA)]

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

Vira Vitanska updated DLAB-523:
---
Description: 
*Preconditions:*

1. DeepLearning is created

 

*Steps to reproduce:*
 # Create Data Engine on DeepLerning

 

*Actual result:*

Data Engine creation fails

!Data Engine.PNG!  

 

*Expected result:*

Data Engine is created

 

  was:
*Preconditions:*

1. DeepLearning is created

 

*Steps to reproduce:*
 # Create Data Engine on DeepLerning

 

*Actual result:*

Data Engine creation fails

 

*Expected result:*

Data Engine is created

 


> [GCP][DeepLearning]: Data Engine creation fails
> ---
>
> Key: DLAB-523
> URL: https://issues.apache.org/jira/browse/DLAB-523
> Project: Apache DLab
>  Issue Type: Bug
>  Components: GCP
>Reporter: Vira Vitanska
>Assignee: Oleksandr Isniuk
>Priority: Major
>  Labels: Debian, DevOps, GCP_demo
> Fix For: v.2.2
>
> Attachments: Data Engine.PNG
>
>
> *Preconditions:*
> 1. DeepLearning is created
>  
> *Steps to reproduce:*
>  # Create Data Engine on DeepLerning
>  
> *Actual result:*
> Data Engine creation fails
> !Data Engine.PNG!  
>  
> *Expected result:*
> Data Engine is created
>  



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

-
To unsubscribe, e-mail: dev-unsubscr...@dlab.apache.org
For additional commands, e-mail: dev-h...@dlab.apache.org

[jira] [Created] (DLAB-523) [GCP][DeepLearning]: Data Engine creation fails

[Vira Vitanska (JIRA)]

Vira Vitanska created DLAB-523:
--

 Summary: [GCP][DeepLearning]: Data Engine creation fails
 Key: DLAB-523
 URL: https://issues.apache.org/jira/browse/DLAB-523
 Project: Apache DLab
  Issue Type: Bug
  Components: GCP
Reporter: Vira Vitanska
Assignee: Oleksandr Isniuk
 Fix For: v.2.2
 Attachments: Data Engine.PNG

*Preconditions:*

1. DeepLearning is created

 

*Steps to reproduce:*
 # Create Data Engine on DeepLerning

 

*Actual result:*

Data Engine creation fails

 

*Expected result:*

Data Engine is created

 



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

-
To unsubscribe, e-mail: dev-unsubscr...@dlab.apache.org
For additional commands, e-mail: dev-h...@dlab.apache.org

[jira] [Updated] (DLAB-473) 'Caffe' doesn’t run successfully on Deep Learning

[Vira Vitanska (JIRA)]

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

Vira Vitanska updated DLAB-473:
---
Summary: 'Caffe' doesn’t run successfully on Deep Learning  (was: 
Visualization playbook doesn’t run successfully on Deep Learning)

> 'Caffe' doesn’t run successfully on Deep Learning
> -
>
> Key: DLAB-473
> URL: https://issues.apache.org/jira/browse/DLAB-473
> Project: Apache DLab
>  Issue Type: Bug
>  Components: AWS, Azure, GCP
>Reporter: Anna Orlovska
>Assignee: Oleksandr Isniuk
>Priority: Major
>  Labels: Debian, DevOps
> Fix For: v.2.2
>
> Attachments: failed_data_viz_Caffe_on_DeLer.png
>
>
> *Preconditions:*
>  Deep Learning is created and running.
> *Steps to reproduce:*
>  1. Open notebook URL in browser.
> 2. Upload file “Caffe.ipynb”.
> 3. Choose Local PySpark (Python-2.7 / Spark-2.3.2 ) kernel.
> 4. Run playbook.
> *Expected result:*
>  Playbook is run successfully. 
> *Actual result:*
>  Playbook doesn’t run successfully.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

-
To unsubscribe, e-mail: dev-unsubscr...@dlab.apache.org
For additional commands, e-mail: dev-h...@dlab.apache.org

[jira] [Updated] (DLAB-473) 'Caffe' doesn’t run successfully on Deep Learning

[Vira Vitanska (JIRA)]

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

Vira Vitanska updated DLAB-473:
---
Labels: Debian DevOps GCP_demo  (was: Debian DevOps)

> 'Caffe' doesn’t run successfully on Deep Learning
> -
>
> Key: DLAB-473
> URL: https://issues.apache.org/jira/browse/DLAB-473
> Project: Apache DLab
>  Issue Type: Bug
>  Components: AWS, Azure, GCP
>Reporter: Anna Orlovska
>Assignee: Oleksandr Isniuk
>Priority: Major
>  Labels: Debian, DevOps, GCP_demo
> Fix For: v.2.2
>
> Attachments: failed_data_viz_Caffe_on_DeLer.png
>
>
> *Preconditions:*
>  Deep Learning is created and running.
> *Steps to reproduce:*
>  1. Open notebook URL in browser.
> 2. Upload file “Caffe.ipynb”.
> 3. Choose Local PySpark (Python-2.7 / Spark-2.3.2 ) kernel.
> 4. Run playbook.
> *Expected result:*
>  Playbook is run successfully. 
> *Actual result:*
>  Playbook doesn’t run successfully.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

-
To unsubscribe, e-mail: dev-unsubscr...@dlab.apache.org
For additional commands, e-mail: dev-h...@dlab.apache.org

[jira] [Updated] (DLAB-473) Visualization playbook doesn’t run successfully on Deep Learning

[Vira Vitanska (JIRA)]

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

Vira Vitanska updated DLAB-473:
---
Component/s: GCP
 Azure

> Visualization playbook doesn’t run successfully on Deep Learning
> 
>
> Key: DLAB-473
> URL: https://issues.apache.org/jira/browse/DLAB-473
> Project: Apache DLab
>  Issue Type: Bug
>  Components: AWS, Azure, GCP
>Reporter: Anna Orlovska
>Assignee: Oleksandr Isniuk
>Priority: Major
>  Labels: Debian, DevOps
> Fix For: v.2.2
>
> Attachments: failed_data_viz_Caffe_on_DeLer.png
>
>
> *Preconditions:*
>  Deep Learning is created and running.
> *Steps to reproduce:*
>  1. Open notebook URL in browser.
> 2. Upload file “Caffe.ipynb”.
> 3. Choose Local PySpark (Python-2.7 / Spark-2.3.2 ) kernel.
> 4. Run playbook.
> *Expected result:*
>  Playbook is run successfully. 
> *Actual result:*
>  Playbook doesn’t run successfully.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

-
To unsubscribe, e-mail: dev-unsubscr...@dlab.apache.org
For additional commands, e-mail: dev-h...@dlab.apache.org

[jira] [Assigned] (DLAB-473) Visualization playbook doesn’t run successfully on Deep Learning

[Vira Vitanska (JIRA)]

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

Vira Vitanska reassigned DLAB-473:
--

Assignee: Oleksandr Isniuk  (was: Oleh Martushevskyi)

> Visualization playbook doesn’t run successfully on Deep Learning
> 
>
> Key: DLAB-473
> URL: https://issues.apache.org/jira/browse/DLAB-473
> Project: Apache DLab
>  Issue Type: Bug
>  Components: AWS
>Reporter: Anna Orlovska
>Assignee: Oleksandr Isniuk
>Priority: Major
>  Labels: Debian, DevOps
> Fix For: v.2.2
>
> Attachments: failed_data_viz_Caffe_on_DeLer.png
>
>
> *Preconditions:*
>  Deep Learning is created and running.
> *Steps to reproduce:*
>  1. Open notebook URL in browser.
> 2. Upload file “Caffe.ipynb”.
> 3. Choose Local PySpark (Python-2.7 / Spark-2.3.2 ) kernel.
> 4. Run playbook.
> *Expected result:*
>  Playbook is run successfully. 
> *Actual result:*
>  Playbook doesn’t run successfully.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

-
To unsubscribe, e-mail: dev-unsubscr...@dlab.apache.org
For additional commands, e-mail: dev-h...@dlab.apache.org

[jira] [Created] (DLAB-522) [AWS]: Refactor Endpoint/Route table creation for SSN

[Oleh Martushevskyi (JIRA)]

Oleh Martushevskyi created DLAB-522:
---

 Summary: [AWS]: Refactor Endpoint/Route table creation for SSN 
 Key: DLAB-522
 URL: https://issues.apache.org/jira/browse/DLAB-522
 Project: Apache DLab
  Issue Type: Bug
Reporter: Oleh Martushevskyi
Assignee: Oleh Martushevskyi


Currently, we are looking for route table with specific tags.

We should check the existence of route table for VPC and S3 endpoint.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

-
To unsubscribe, e-mail: dev-unsubscr...@dlab.apache.org
For additional commands, e-mail: dev-h...@dlab.apache.org

[jira] [Commented] (DLAB-52) [GCP]: Failed edge removes a shared bucket

[Vira Vitanska (JIRA)]

[ 
https://issues.apache.org/jira/browse/DLAB-52?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16790465#comment-16790465
 ] 

Vira Vitanska commented on DLAB-52:
---

Commit ID 529cc7701efb9043b226da90f9367eb221878599

> [GCP]: Failed edge removes a shared bucket
> --
>
> Key: DLAB-52
> URL: https://issues.apache.org/jira/browse/DLAB-52
> Project: Apache DLab
>  Issue Type: Bug
>  Components: GCP
> Environment: GCP
>Reporter: Vira Vitanska
>Assignee: Oleh Martushevskyi
>Priority: Critical
>  Labels: Debian, DevOps, GCP_demo
> Fix For: v.2.2
>
> Attachments: Edge creation again.PNG, Logs of create edge again.txt, 
> Logs of failed edge.txt, Shared bucket.PNG, 
> backup_8b8dc7a5-c290-49ec-a9f2-9acb952f8a29.tar.gz, image.png, image.png
>
>
> A bug was found on GCP.  Edge creation fails on a process creating ssh user. 
> Failing edge deletes shared bucket. After that it is impossible to create a 
> new edge for user.
> !Edge creation again.PNG!
> *Preconditions:*
> 1. SSN is created
>  
> *Steps to reproduce:*
> 1. Fail SSN on stage of creating ssh user
>  
> *Actual result:*
> Shared bucket is deleted
> !Shared bucket.PNG!
> *Expected result:*
> Shared bucket is not deleted
>  



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

-
To unsubscribe, e-mail: dev-unsubscr...@dlab.apache.org
For additional commands, e-mail: dev-h...@dlab.apache.org

[jira] [Created] (DLAB-521) Add support of local repository to downloading toree on SSN

[Oleh Martushevskyi (JIRA)]

Oleh Martushevskyi created DLAB-521:
---

 Summary: Add support of local repository to downloading toree on 
SSN 
 Key: DLAB-521
 URL: https://issues.apache.org/jira/browse/DLAB-521
 Project: Apache DLab
  Issue Type: Sub-task
Reporter: Oleh Martushevskyi
Assignee: Oleh Martushevskyi






--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

-
To unsubscribe, e-mail: dev-unsubscr...@dlab.apache.org
For additional commands, e-mail: dev-h...@dlab.apache.org

[GitHub] [incubator-dlab] OlehMartushevskyi merged pull request #29: Epmcdlab 328

[GitBox]

OlehMartushevskyi merged pull request #29: Epmcdlab 328
URL: https://github.com/apache/incubator-dlab/pull/29
 
 
   


This is an automated message from the Apache Git Service.
To respond to the message, please log on to 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


With regards,
Apache Git Services

-
To unsubscribe, e-mail: dev-unsubscr...@dlab.apache.org
For additional commands, e-mail: dev-h...@dlab.apache.org

[jira] [Updated] (DLAB-318) [GCP]: DeepLearning creation Fails on configure.py process

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot updated DLAB-318:

Labels: Debian DevOps GCP_demo pull-request-available  (was: Debian DevOps 
GCP_demo)

> [GCP]: DeepLearning creation Fails on configure.py process
> --
>
> Key: DLAB-318
> URL: https://issues.apache.org/jira/browse/DLAB-318
> Project: Apache DLab
>  Issue Type: Bug
>  Components: GCP
>Reporter: Vira Vitanska
>Assignee: Oleksandr Isniuk
>Priority: Major
>  Labels: Debian, DevOps, GCP_demo, pull-request-available
> Fix For: v.2.2
>
> Attachments: DeepL.png, DeepLearning creation.PNG
>
>
> *Preconditions:*
> 1. Edge is created
>  
> *Steps to reproduce:*
> 1. Create Deeplearning
>  
> *Actual result:*
> Deeplearning creation fails with error:
> !DeepLearning creation.PNG!
> *Expected result:*
> DeepLearning is created
>  
>  
> Note: Now by date 14-01-2019 Deeplerning creation fails on stage:
> !DeepL.png!



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

-
To unsubscribe, e-mail: dev-unsubscr...@dlab.apache.org
For additional commands, e-mail: dev-h...@dlab.apache.org

[GitHub] [incubator-dlab] OlehMartushevskyi merged pull request #30: [DLAB-318] fix DeepLearning creation for GCP

[GitBox]

OlehMartushevskyi merged pull request #30: [DLAB-318] fix DeepLearning creation 
for GCP
URL: https://github.com/apache/incubator-dlab/pull/30
 
 
   


This is an automated message from the Apache Git Service.
To respond to the message, please log on to 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


With regards,
Apache Git Services

-
To unsubscribe, e-mail: dev-unsubscr...@dlab.apache.org
For additional commands, e-mail: dev-h...@dlab.apache.org

[GitHub] [incubator-dlab] ioleksandr opened a new pull request #30: [DLAB-318] fix DeepLearning creation for GCP

[GitBox]

ioleksandr opened a new pull request #30: [DLAB-318] fix DeepLearning creation 
for GCP
URL: https://github.com/apache/incubator-dlab/pull/30
 
 
   


This is an automated message from the Apache Git Service.
To respond to the message, please log on to 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


With regards,
Apache Git Services

-
To unsubscribe, e-mail: dev-unsubscr...@dlab.apache.org
For additional commands, e-mail: dev-h...@dlab.apache.org