Terraform GUI
a project by kevinklinger
Updated over 4 years ago. 4 hacker ♥️. 4 followers.

Project Description

Build a tool that provides a GUI for Terraform and is able to spin up machines directly on KVM. The user should not be required to have any Terraform skills and should be guided through the GUI when he wants to create new Terraform scripts. Furthermore it would be helpful if the tool could export its configuration to HCL.

Goal for this Hackweek

Having at least a prototype that can spin up simple machine configurations.

Resources

The libivrt provider for Terraform should be used:
https://github.com/dmacvicar/terraform-provider-libvirt

Join this project

Looking for hackers with the skills:

golang terraform frontend

This project is part of:

Hack Week 20

Activity

  • over 1 year ago: polinkuer12 joined this project.
  • over 4 years ago: acho liked this project.
  • over 4 years ago: equill liked this project.
  • over 4 years ago: kevinklinger added keyword "frontend" to this project.
  • over 4 years ago: ories liked this project.
  • over 4 years ago: berndschubert joined this project.
  • over 4 years ago: kevinklinger started this project.
  • over 4 years ago: ph03nix liked this project.
  • over 4 years ago: kevinklinger added keyword "golang" to this project.
  • over 4 years ago: kevinklinger added keyword "terraform" to this project.
  • over 4 years ago: kevinklinger originated this project.


    • Comments

    • dominic_vieira
      over 4 years ago by dominic_vieira | Reply

      Have you looked at the Blue Horizon project? This was created by the Public Cloud Engineering Team - https://github.com/SUSE-Enceladus/blue-horizon

    • kevinklinger
      over 4 years ago by kevinklinger | Reply

      @dominic_vieira I think the difference is that Blue Horizon requires that you have the desired scripts already coded. This GUI I'm thinking of would be something to guide the user through the process of creating Terraform scripts.

      But thanks for the link add-emoji

    • pagarcia
      over 4 years ago by pagarcia | Reply

      If you don't want to build the UI from scratch but rather focus on the HCL-generation problem, this might come handy: https://appsmith.com/ https://github.com/appsmithorg/appsmith

      Add new widgets for Terraform-related concepts, then generate HCL from that.

      The inverse (HCL to UI) is even more interesting :-)

    • polinkuer12
      over 1 year ago by polinkuer12 | Reply

      I want to redraft that prototype in Quick Draw

    Similar Projects

    terraform-provider-feilong by e_bischoff

    Project Description

    People need to test operating systems and applications on s390 platform.

    Installation from scratch solutions include:

    • just deploy and provision manually add-emoji (with the help of ftpboot script, if you are at SUSE)
    • use s3270 terminal emulation (used by openQA people?)
    • use LXC from IBM to start CP commands and analyze the results
    • use zPXE to do some PXE-alike booting (used by the orthos team?)
    • use tessia to install from scratch using autoyast
    • use libvirt for s390 to do some nested virtualization on some already deployed z/VM system
    • directly install a Linux kernel on a LPAR and use kvm + libvirt from there

    Deployment from image solutions include:

    • use ICIC web interface (openstack in disguise, contributed by IBM)
    • use ICIC from the openstack terraform provider (used by Rancher QA)
    • use zvm_ansible to control SMAPI
    • connect directly to SMAPI low-level socket interface

    IBM Cloud Infrastructure Center (ICIC) harnesses the Feilong API, but you can use Feilong without installing ICIC, provided you set up a "z/VM cloud connector" into one of your VMs following this schema.

    What about writing a terraform Feilong provider, just like we have the terraform libvirt provider? That would allow to transparently call Feilong from your main.tf files to deploy and destroy resources on your system/z.

    Other Feilong-based solutions include:

    • make libvirt Feilong-aware
    • simply call Feilong from shell scripts with curl
    • use zvmconnector client python library from Feilong
    • use zthin part of Feilong to directly command SMAPI.

    Goal for Hackweek 23

    My final goal is to be able to easily deploy and provision VMs automatically on a z/VM system, in a way that people might enjoy even outside of SUSE.

    My technical preference is to write a terraform provider plugin, as it is the approach that involves the least software components for our deployments, while remaining clean, and compatible with our existing development infrastructure.

    Goals for Hackweek 24

    Feilong provider works and is used internally by SUSE Manager team. Let's push it forward!

    Let's add support for fiberchannel disks and multipath.

    Possible goals for Hackweek 25

    Modernization, maturity, and maintenance.

    terraform-provider-feilong by e_bischoff

    Project Description

    People need to test operating systems and applications on s390 platform.

    Installation from scratch solutions include:

    • just deploy and provision manually add-emoji (with the help of ftpboot script, if you are at SUSE)
    • use s3270 terminal emulation (used by openQA people?)
    • use LXC from IBM to start CP commands and analyze the results
    • use zPXE to do some PXE-alike booting (used by the orthos team?)
    • use tessia to install from scratch using autoyast
    • use libvirt for s390 to do some nested virtualization on some already deployed z/VM system
    • directly install a Linux kernel on a LPAR and use kvm + libvirt from there

    Deployment from image solutions include:

    • use ICIC web interface (openstack in disguise, contributed by IBM)
    • use ICIC from the openstack terraform provider (used by Rancher QA)
    • use zvm_ansible to control SMAPI
    • connect directly to SMAPI low-level socket interface

    IBM Cloud Infrastructure Center (ICIC) harnesses the Feilong API, but you can use Feilong without installing ICIC, provided you set up a "z/VM cloud connector" into one of your VMs following this schema.

    What about writing a terraform Feilong provider, just like we have the terraform libvirt provider? That would allow to transparently call Feilong from your main.tf files to deploy and destroy resources on your system/z.

    Other Feilong-based solutions include:

    • make libvirt Feilong-aware
    • simply call Feilong from shell scripts with curl
    • use zvmconnector client python library from Feilong
    • use zthin part of Feilong to directly command SMAPI.

    Goal for Hackweek 23

    My final goal is to be able to easily deploy and provision VMs automatically on a z/VM system, in a way that people might enjoy even outside of SUSE.

    My technical preference is to write a terraform provider plugin, as it is the approach that involves the least software components for our deployments, while remaining clean, and compatible with our existing development infrastructure.

    Goals for Hackweek 24

    Feilong provider works and is used internally by SUSE Manager team. Let's push it forward!

    Let's add support for fiberchannel disks and multipath.

    Possible goals for Hackweek 25

    Modernization, maturity, and maintenance.