question-mark
Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

[BUG] The default values can't be changed in cluster config file for virtual machine.

See original GitHub issue

Describe the bug It is not possible to change default values in configuration section for infrastructure/virtual-machine such as:

  • disk_size_gb
  • offer
  • sku etc… in cluster config file. Terraform use always default ones.

How to reproduce Steps to reproduce the behavior:

  1. execute epicli init ... (with params)
  2. edit config file and change default os_disk_size or os image
  3. execute epicli apply ...

Expected behavior I would like to create cluster with the values which I set in my configuration file. If I set 64GB os disk size, I would like to have 64GB os disk size, not the default 32GB

Config files

---
kind: infrastructure/virtual-machine
title: Virtual Machine Infra
provider: azure
name: default
specification:
  tags: []
  os_type: linux
  size: Standard_DS1_v2
  storage_image_reference:
    publisher: Canonical
    offer: UbuntuServer
    sku: 18_04-lts-gen2
    version: 18.04.202101290
  storage_os_disk:
    delete_on_termination: false
    managed: false
    caching: ReadWrite
    create_option: FromImage
    disk_size_gb: 64
    managed_disk_type: Premium_LRS

Environment

  • Cloud provider: [AWS | Azure]
  • OS: [all]

epicli version: 0.9

Additional context Add any other context about the problem here.


DoD checklist

  • Changelog updated (if affected version was released)
  • COMPONENTS.md updated / doesn’t need to be updated
  • Automated tests passed (QA pipelines)
    • apply
    • upgrade
  • Case covered by automated test (if possible)
  • Idempotency tested
  • Documentation updated / doesn’t need to be updated
  • All conversations in PR resolved

Issue Analytics

  • State:closed
  • Created 3 years ago
  • Comments:5 (2 by maintainers)

github_iconTop GitHub Comments

1reaction
przemyslaviccommented, Mar 4, 2021

@rpudlowski93 For now, the only option to change these parameters is to provide the configuration for each vm like this:

---
kind: epiphany-cluster
name: default
provider: azure
specification:
  admin_user:
    key_path: /path/to/id_rsa
    name: operations
  cloud:
    region: West Europe
    subscription_name: xxx
    use_public_ips: false
    use_service_principal: true   
  components:
    kafka:
      count: 2
      machine: kafka-machine-rhel
    kubernetes_master:
      count: 1
      machine: kubernetes-master-machine-rhel
    kubernetes_node:
      count: 2
      machine: kubernetes-node-machine-rhel
    load_balancer:
      count: 1
      machine: lb-machine-rhel  
    logging:
      count: 2
      machine: logging-machine-rhel
    monitoring:
      count: 1
      machine: monitoring-machine-rhel
    postgresql:
      count: 2
      machine: postgresql-machine-rhel
    rabbitmq:
      count: 2
      machine: rabbitmq-machine-rhel
    ignite:
      count: 2
      machine: ignite-machine-rhel
    opendistro_for_elasticsearch:
      count: 2
      machine:  opendistro-machine-rhel
    repository:
      count: 1
      machine:  repository-machine-rhel
  name: test
  prefix: 'qa'
title: Epiphany cluster Config
---
kind: infrastructure/virtual-machine
name: kafka-machine-rhel
provider: azure
based_on: kafka-machine
specification:
  storage_image_reference:
    publisher: RedHat
    offer: RHEL
    sku: 7-LVM
    version: "7.9.2020111202"
  storage_os_disk:
    disk_size_gb: 64
---
kind: infrastructure/virtual-machine
name: kubernetes-master-machine-rhel
provider: azure
based_on: kubernetes-master-machine
specification:
  storage_image_reference:
    publisher: RedHat
    offer: RHEL
    sku: 7-LVM
    version: "7.9.2020111202"
  storage_os_disk:
    disk_size_gb: 64
---
kind: infrastructure/virtual-machine
name: kubernetes-node-machine-rhel
provider: azure
based_on: kubernetes-node-machine
specification:
  storage_image_reference:
    publisher: RedHat
    offer: RHEL
    sku: 7-LVM
    version: "7.9.2020111202"
  storage_os_disk:
    disk_size_gb: 64
---
kind: infrastructure/virtual-machine
name: logging-machine-rhel
provider: azure
based_on: logging-machine
specification:
  storage_image_reference:
    publisher: RedHat
    offer: RHEL
    sku: 7-LVM
    version: "7.9.2020111202"
  storage_os_disk:
    disk_size_gb: 64
---
kind: infrastructure/virtual-machine
name: monitoring-machine-rhel
provider: azure
based_on: monitoring-machine
specification:
  storage_image_reference:
    publisher: RedHat
    offer: RHEL
    sku: 7-LVM
    version: "7.9.2020111202"
  storage_os_disk:
    disk_size_gb: 64
---
kind: infrastructure/virtual-machine
name: postgresql-machine-rhel
provider: azure
based_on: postgresql-machine
specification:
  storage_image_reference:
    publisher: RedHat
    offer: RHEL
    sku: 7-LVM
    version: "7.9.2020111202"
  storage_os_disk:
    disk_size_gb: 64
---
kind: infrastructure/virtual-machine
name: lb-machine-rhel
provider: azure
based_on: load-balancer-machine
specification:
  storage_image_reference:
    publisher: RedHat
    offer: RHEL
    sku: 7-LVM
    version: "7.9.2020111202"
  storage_os_disk:
    disk_size_gb: 64
---
kind: infrastructure/virtual-machine
name: rabbitmq-machine-rhel
provider: azure
based_on: rabbitmq-machine
specification:
  storage_image_reference:
    publisher: RedHat
    offer: RHEL
    sku: 7-LVM
    version: "7.9.2020111202"
  storage_os_disk:
    disk_size_gb: 64
---
kind: infrastructure/virtual-machine
name: ignite-machine-rhel
provider: azure
based_on: ignite-machine
specification:
  storage_image_reference:
    publisher: RedHat
    offer: RHEL
    sku: 7-LVM
    version: "7.9.2020111202"
  storage_os_disk:
    disk_size_gb: 64
---
kind: infrastructure/virtual-machine
name: opendistro-machine-rhel
provider: azure
based_on: logging-machine
specification:
  storage_image_reference:
    publisher: RedHat
    offer: RHEL
    sku: 7-LVM
    version: "7.9.2020111202"
  storage_os_disk:
    disk_size_gb: 64
---
kind: infrastructure/virtual-machine
name: repository-machine-rhel
provider: azure
based_on: repository-machine
specification:
  storage_image_reference:
    publisher: RedHat
    offer: RHEL
    sku: 7-LVM
    version: "7.9.2020111202"
  storage_os_disk:
    disk_size_gb: 64
0reactions
przemyslaviccommented, Apr 28, 2021

✔️ Fixed. Now we can easily change the default values for OS image, vm size, disk size, etc.

Read more comments on GitHub >

github_iconTop Results From Across the Web

The Default Virtual Machine Configuration Store Cannot be ...
I am trying to change the default virtual machine configuration store from within the hyper-v settings to a SMB 3.0 share.
Read more >
2000770 – Failed to Change Cluster settings - Red Hat Bugzilla
To fix the issue, please go to each of them, edit, change the Custom Compatibility Version (or other fields changed previously in the...
Read more >
Changed Block Tracking (CBT) on virtual machines (1020128)
Right-click the virtual machine and navigate to Edit Settings > Options > Advanced/General > Configuration Parameters. CBT Changed Block ...
Read more >
How to Fix the Error Hyper-V failed to Change State - NAKIVO
This blog post explains possible reasons for the “Hyper-V failed to change state” error and the methods available for resolving this issue.
Read more >
8.128 Editing Virtual Machine Configuration File Results in ...
For example, if you edit the HA setting in the vm.cfg to disable HA, and the virtual machine is stopped by any method...
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Dev.to Post

No results found

github_iconTop Related Hashnode Post

No results found