Update Rancher Terraform Quickstart to leverage Elastic IP addresses
a project by kevinmayres
Updated almost 2 years ago. 1 hackers ♥️. 2 followers.

Make Rancher and NeuVector AWS QuickStart persistent across Shutdown.

Specifically update this AWS portion of the QuickStart to leverage Amazon Elastic IP Addresses, making the stack persistent across shutdowns startups. Designed to save budget when not using. While Terraform is designed to build and tear-down, sometimes we add additional customizations post-build which we want to be persistent for the next demo, PoC, or development experiment. Not losing the public IP assigned to cluster API, etc. would allow persistency across shutdown.

Additionally, we could include code to create and leverage persistent storage for Rancher and NV, deploy Longhorn, launch a downstream EKS or EKS-Anywhere test cluster or experiment with zero node managed node-groups or Spot based node-groups, as a stretch goal.. possibly.

https://github.com/rancher/quickstart

https://github.com/rancher/quickstart/issues/223

Seeking: Anyone with Terraform or Amazon Cloudformation familiarity Keywords: Rancher NeuVector AWS Terraform Cloudformation Demo PoC

Join this project

Looking for hackers with the skills:

terraform cloudformation

This project is part of:

Hack Week 23

Activity

  • almost 2 years ago: pschinagl started this project.
  • almost 2 years ago: kevinmayres added keyword "terraform" to this project.
  • almost 2 years ago: kevinmayres added keyword "cloudformation" to this project.
  • almost 2 years ago: kevinmayres liked this project.
  • almost 2 years ago: kevinmayres originated this project.


    • Comments

    Be the first to comment!

    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.