Skip to content
This repository has been archived by the owner on Feb 15, 2022. It is now read-only.

Cluster/Infra Creation Epic #585

Closed
18 of 22 tasks
andrebriggs opened this issue Sep 10, 2019 · 5 comments
Closed
18 of 22 tasks

Cluster/Infra Creation Epic #585

andrebriggs opened this issue Sep 10, 2019 · 5 comments
Labels
effort - XL really needs to be broken up epic An "epic" story that holds several related issues

Comments

@andrebriggs
Copy link
Member

andrebriggs commented Sep 10, 2019

Spikes

Terraform work

CLI Work

Considerations:

  • What happens if I move from machine A to machine B, where does the spk state live?
  • What happens if the remote bedrock environment changes?
  • What happens if I want to update a particular variable/etc?
@andrebriggs
Copy link
Member Author

Create a state file for initialization (in ~/.spk)

Have we checked with the other groups about their need for cached data?

Clone official/custom Bedrock repo using -p argument

Are we requiring that a custom repo follows the same Bedrock directory structure?

Generates an infrastructure "HLD" (e.g. infra.json/yaml)

What exactly will be in here?

CC @yradsmikham @NathanielRose

@NathanielRose
Copy link
Contributor

NathanielRose commented Sep 27, 2019

@andrebriggs
Have we checked with the other groups about their need for cached data?

  • No we have not, will definitely surface if their is a need for other teams as well. Our thinking was targeting spk infra init then migrate to a spk init that calls other command initializations such as spk project init + spk deployment init

Are we requiring that a custom repo follows the same Bedrock directory structure?

  • We are at the moment. This can later be migrated to sparse cloning a repo based on a bedrock environment path to be passed to our spk infra create

What exactly will be in here?

  • Our Brainstorm YAML:
---
Bedrock_Repo: True
Deployment_Name: Azure-ECK-Simple
Terraform_Version: 0.12.3
Bedrock_Source: (URL/LocalPath)
Data_Resources: [resource_group_name]
TFvars: 
{
resource_group_name      = "resource-group-name"
cluster_name             = "cluster-name"
agent_vm_count           = "3"
dns_prefix               = "dns-prefix"
service_principal_id     = "client-id"
service_principal_secret = "client-secret"
ssh_public_key           = "public-key"
gitops_ssh_url           = "[email protected]:timfpark/fabrikate-cloud-native-manifests.git"
gitops_ssh_key           = "<path to private gitops repo key>"
vnet_name                = "<vnet name>"
}

CC @yradsmikham @NathanielRose

@yradsmikham
Copy link
Contributor

@andrebriggs

After reaching out to other teams, it appears that there could be a need to have some sort of "cached data". Service Introspection may need store keys, and Service Creation potentially may need to store spk logs or PATs. Regardless, there is a need (currently) for infra.

@NathanielRose
Copy link
Contributor

@andrebriggs @yradsmikham Can this be closed?

@yradsmikham
Copy link
Contributor

@andrebriggs @yradsmikham Can this be closed?

Yes, it looks complete.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
effort - XL really needs to be broken up epic An "epic" story that holds several related issues
Projects
None yet
Development

No branches or pull requests

3 participants