terraform-provider-libvirt
nixpkgs
terraform-provider-libvirt | nixpkgs | |
---|---|---|
13 | 975 | |
1,513 | 15,753 | |
- | 2.2% | |
6.8 | 10.0 | |
13 days ago | about 4 hours ago | |
Go | Nix | |
Apache License 2.0 | MIT License |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
terraform-provider-libvirt
- What do y'all use to provision KVM VM's?
-
libvirt-k8s-provisioner - Ansible and terraform to build a cluster from scratch in less than 10 minutes ok KVM - Updated for 1.26
libvirt-terraform-provider ( based on https://github.com/dmacvicar/terraform-provider-libvirt )
- NixOS 22.11 “Raccoon” Released
-
libvirt-ocp4-provisioner - Provision an OCP 4.x.y cluster in minutes with Ansible, now with Single Node OCP support! .
Hi guys!I wanted to allotment with you a tool to provision a fully working OCP 4.x.y cluster in minutes using Ansible for automation, libvirt as virtualization provider and terraform as VMs templating and creation tool. https://github.com/kubealex/libvirt-ocp4-provisioner It will take care of all the infrastructure provisioning and OCP machines provisioning, starting and completing the UPI installation of a cluster. (IPI work in progress ;) ) To give a quick overview, this project will allow you to provision a fully working OCP stable environment, consisting of: * Bastion machine provisioned with: * dnsmasq (with SELinux module, compiled and activated) * dhcp based on dnsmasq * nginx (for ignition files and rhcos pxe-boot) * pxeboot * Loadbalancer machine provisioned with: * haproxy * OCP Bootstrap machine * OCP Master(s) VM(s) * OCP Worker(s) VM(s) From latest release, it also supports installing SNO on a single host! It also takes care of preparing the host machine with needed packages, configuring: * dedicated libvirt network (fully customizable) * dedicated libvirt storage pool (fully customizable) * terraform * libvirt-terraform-provider ( compiled and initialized basedon https://github.com/dmacvicar/terraform-provider-libvirt) PXE is automatic, based on MAC binding to different OCP nodes role, so no need of choosing it from the menus, this means you can just run the playbook, take a beer and have your fully running OCP 4.9.latest stable up and running. It has been tested on Fedora 3x and CentOS 7/8. Playing around with it and contributions to make it work even on different OSes is more than welcome, hope you enjoy it! Alex
-
Need help on Terraform with KVM/Libvirt
I learned and got terraform to work with the KVM/Libvirt provider.
-
Automate creation of KVM VM and Installation of OS
I saw Terraform with the dmacvicar/terraform-provider-libvirt provider, but sadly didn't get really warm with it. When some can explain to me how I can set up new images for every VM I would be very happy also there are more question in the pipeline. Sadly, the “Documentation” is not really that good. Maybe Terraform is also the wrong Application for me. I'm a little lost because I thought Terraform would be the big Solution I want and need, until now, not yet.
-
Terraform Persistent Storage
It looks like there was an issue dealing with "attaching an existing disk" to a terraform created VM. That's here: https://github.com/dmacvicar/terraform-provider-libvirt/issues/688
-
Those of you running a home cluster that is NOT comprised of RasPis, what hardware are you using?
Nice. I’m straight KVM as it’s a mirror of work (my Lab) and I’m using the terraform-provider-libvirt provider. 20 minutes to fully build a site. Pretty cool.
-
Provision a full functional cluster in less than 10 minutes! libvirt-k8s-provisioner
libvirt-terraform-provider ( compiled and initialized based on https://github.com/dmacvicar/terraform-provider-libvirt)
- QEMU Version 6.0.0 Released
nixpkgs
-
Nix: The Breaking Point
I don't think so. The article is probably intended for the Nix community, so the author doesn't need to convince HN that something is going on. If as an outsider you are interested then you need to look into it yourself, the community has no obligation to make their internal conflicts legible to the outside world.
As an outsider myself, it certainly looks like something is going on as more than 20 Nixpkg maintainers left in a week: https://github.com/NixOS/nixpkgs/issues?q=label%3A%228.has%3...
- Maintainers Leaving
-
Air Force picks Anduril, General Atomics to develop unmanned fighter jets
https://github.com/NixOS/nixpkgs/commits?author=neon-sunset
-
Eelco Dolstra's leadership is corrosive to the Nix project
I see two signers in the top 6 displayed on https://github.com/NixOS/nixpkgs/graphs/contributors
-
3rd Edition of Programming: Principles and Practice Using C++ by Stroustrup
For a single file script, nix can make the package management quite easy: https://github.com/NixOS/nixpkgs/blob/master/doc/languages-f...
For example,
```
- NixOS/nixpkgs: There isn't a clear canonical way to refer to a specific package
-
NixOS Is Not Reproducible
Yes, Nix doesn't actually ensure that the builds are deterministic. In fact it works just fine if they aren't. There are packages in nixpkgs that aren't reproducible: https://github.com/NixOS/nixpkgs/issues?q=is%3Aopen+is%3Aiss...
-
The xz attack shell script
I'm not familiar with Bazel, but Nix in it's current form wouldn't have solved this attack. First of all, the standard mkDerivation function calls the same configure; make; make install process that made this attack possible. Nixpkgs regularly pulls in external resources (fetchUrl and friends) that are equally vulnerable to a poisoned release tarball. Checkout the comment on the current xz entry in nixpkgs https://github.com/NixOS/nixpkgs/blob/master/pkgs/tools/comp...
-
Debian Git Monorepo
NixOS uses a monorepo and I think everyone's love it.
I love being able to easily grep through all the packages source code and there's regularly PRs that harmonizes conventions across many packages.
Nixpkgs doesn't include the packaged software source code, so it's a lot more practical than what Debian is doing.
https://github.com/NixOS/nixpkgs
-
From xz to ibus: more questionable tarballs
In this specific case, nix uses fetchFromGitHub to download the source archive, which are generated by GitHub for the specified revision[1]. Arch seems to just download the tarball from the releases page[2].
[1]: https://github.com/NixOS/nixpkgs/blob/3c2fdd0a4e6396fc310a6e...
[2]: https://gitlab.archlinux.org/archlinux/packaging/packages/ib...
What are some alternatives?
UTM - Virtual machines for iOS and macOS
asdf - Extendable version manager with support for Ruby, Node.js, Elixir, Erlang & more
terraform-provider-proxmox - Terraform provider plugin for proxmox
Home Manager using Nix - Manage a user environment using Nix [maintainer=@rycee]
terraform-provider-rancher2 - Terraform Rancher2 provider
git-lfs - Git extension for versioning large files
QEMU - Official QEMU mirror. Please see https://www.qemu.org/contribute/ for how to submit changes to QEMU. Pull Requests are ignored. Please only use release tarballs from the QEMU website.
easyeffects - Limiter, compressor, convolver, equalizer and auto volume and many other plugins for PipeWire applications
libvirt-k8s-provisioner - Automate your k8s installation
spack - A flexible package manager that supports multiple versions, configurations, platforms, and compilers.
xemu - Original Xbox Emulator for Windows, macOS, and Linux (Active Development)
waydroid - Waydroid uses a container-based approach to boot a full Android system on a regular GNU/Linux system like Ubuntu.