<commit_before># Kops tasks and effort estimation

List of open issues and features and their effort estimation as of <time datetime="2017-06-06" class="date-past">06 Jun 2017</time>.

**TODO** Issues listed below require proper labels to be assigned, especially P0.

**Priorities**

P0: Must have fixes and features, needed to make existing vSphere support in kops work.

P1: Important fixes and features, required to give vSphere users a more useful kubernetes cluster deployment experience, with multiple masters and HA.

P2: Rarely occurring issues and features that will bring vSphere support closer to AWS and GCE support in kops.

**Notes:**

*   Effort estimation inclues fix for an issue or implementation for a feature, testing and generating a PR.
*   There are a few issues that are related to startup and base image. If we can resolve "Use PhotonOS for vSphere node template" issue first and replace init-cloud with guestinfo, those issues **might** get resolved automatically. But further investigation is needed and fixed issues will need verifications and testings.

|Priority|Task|Type (bug, feature, test|Effort estimate(in days)|Remarks|
|--- |--- |--- |--- |--- |
|P0|Kops for vSphere is broken kubernetes/kops#2729|Bug|1||
|P0|AWS EBS is set as default volume provisioner, instead of vSphere kubernetes/kops#2732|Bug|1|Looks like the fix is available, need to be tested again before commiting https://github.com/vmware/kops/pull/70/files|
|P0|Package installation through nodeup causing delay in cluster deployment kubernetes/kops#2742|Bug|2|If we get the "Use PhotonOS for vSphere node template" done first, this one may just be avoided. Verification required.|
|P0|Connection to api.clustername.skydns.local is failing  kubernetes/kops#2744|Bug|1|This might be fixed by Abrar's PR in kubernetes already. Just need to verify.|
|P0|Make update command, that includes scale up and down, work kubernetes/kops#2738. There are two possible ways to implement this- without auto scaling group (ASG) or with auto scaling group|Feature|4 days Assuming ASG is available. 4 days ASG is not available.|This effort estimation needs more analysis.|
|P0|Make end-to-end CI/CD work on vmware/kops kubernetes/kops#2730|Bug, Test|3||
|P1|Use PhotonOS for vSphere node template  kubernetes/kops#2735. Use guestinfo instead of init-cloud kubernetes/kops#2726|Feature|5|This was originally P2 issue. However several other issues might be affected by this one. So bring it to P1. Problem to solve: init-cloud on PhotonOS not working properly. Or, get rid of init-cloud and use guestinfo instead.|
|P1|Default image name extraction for vSphere needs to be fixed kubernetes/kops#2740|Bug|2||
|P1|Multi-master HA setup kubernetes/kops#2734|Feature|5||<commit_msg>inclues --> includes<commit_after># Kops tasks and effort estimation

List of open issues and features and their effort estimation as of <time datetime="2017-06-06" class="date-past">06 Jun 2017</time>.

**TODO** Issues listed below require proper labels to be assigned, especially P0.

**Priorities**

P0: Must have fixes and features, needed to make existing vSphere support in kops work.

P1: Important fixes and features, required to give vSphere users a more useful kubernetes cluster deployment experience, with multiple masters and HA.

P2: Rarely occurring issues and features that will bring vSphere support closer to AWS and GCE support in kops.

**Notes:**

*   Effort estimation includes fix for an issue or implementation for a feature, testing and generating a PR.
*   There are a few issues that are related to startup and base image. If we can resolve "Use PhotonOS for vSphere node template" issue first and replace init-cloud with guestinfo, those issues **might** get resolved automatically. But further investigation is needed and fixed issues will need verifications and testings.

|Priority|Task|Type (bug, feature, test|Effort estimate(in days)|Remarks|
|--- |--- |--- |--- |--- |
|P0|Kops for vSphere is broken kubernetes/kops#2729|Bug|1||
|P0|AWS EBS is set as default volume provisioner, instead of vSphere kubernetes/kops#2732|Bug|1|Looks like the fix is available, need to be tested again before commiting https://github.com/vmware/kops/pull/70/files|
|P0|Package installation through nodeup causing delay in cluster deployment kubernetes/kops#2742|Bug|2|If we get the "Use PhotonOS for vSphere node template" done first, this one may just be avoided. Verification required.|
|P0|Connection to api.clustername.skydns.local is failing  kubernetes/kops#2744|Bug|1|This might be fixed by Abrar's PR in kubernetes already. Just need to verify.|
|P0|Make update command, that includes scale up and down, work kubernetes/kops#2738. There are two possible ways to implement this- without auto scaling group (ASG) or with auto scaling group|Feature|4 days Assuming ASG is available. 4 days ASG is not available.|This effort estimation needs more analysis.|
|P0|Make end-to-end CI/CD work on vmware/kops kubernetes/kops#2730|Bug, Test|3||
|P1|Use PhotonOS for vSphere node template  kubernetes/kops#2735. Use guestinfo instead of init-cloud kubernetes/kops#2726|Feature|5|This was originally P2 issue. However several other issues might be affected by this one. So bring it to P1. Problem to solve: init-cloud on PhotonOS not working properly. Or, get rid of init-cloud and use guestinfo instead.|
|P1|Default image name extraction for vSphere needs to be fixed kubernetes/kops#2740|Bug|2||
|P1|Multi-master HA setup kubernetes/kops#2734|Feature|5||
{'fraction_non_alphanumeric': 0.07724312590448625, 'fraction_numerical': 0.02930535455861071, 'mean_word_length': 5.016322089227421, 'pattern_counts': {'":': 0, '<': 7, '<?xml version=': 0, '>': 8, 'https://': 2, 'lorem ipsum': 0, 'www.': 0, 'xml': 0}, 'pii_count': 0, 'substrings_counts': 0, 'word_list_counts': {'cursed_substrings.json': 1, 'profanity_word_list.json': 0, 'sexual_word_list.json': 0, 'zh_pornsignals.json': 0}}
{'dir': 'git-commits-cleaned', 'id': '5696394', 'n_tokens_mistral': 1647, 'n_tokens_neox': 1533, 'n_words': 724}