You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@dlab.apache.org by "Vira Vitanska (JIRA)" <ji...@apache.org> on 2019/03/05 21:42:00 UTC

[jira] [Assigned] (DLAB-396) Refactor Dlab deploying with 2 VPCs

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

Vira Vitanska reassigned DLAB-396:
----------------------------------

    Assignee:     (was: Oleksandr Isniuk)

> Refactor Dlab deploying with 2 VPCs
> -----------------------------------
>
>                 Key: DLAB-396
>                 URL: https://issues.apache.org/jira/browse/DLAB-396
>             Project: Apache DLab
>          Issue Type: Task
>          Components: AWS
>            Reporter: Vira Vitanska
>            Priority: Major
>              Labels: Debian, DevOps, RedHat
>
> Add to .ini some argument to define that vpc connection already created(not just peering)
> Check route tables and ability to use own route table
> Refactor logic of ssn_prepare.py
> Remove aws_notebook_subnet_id mock (co-work with java)
> Ability to add names to peering connection and second VPC
> Problems with terminating of secondary VPC if EMR was provisioned
> Take a look on case with predefined 1st VPC and wrong VPC CIDR



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

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