A weakness is Katello is a huge pain to set up. I literally used forklift to get a Vagrant box up and then used that Vagrant box as a long living VM.

@ccwtech said in Manage KVM through Cockpit:

Sorry if this is a dumb question, I'm very new at Linux in general.

When adding a VM, where do you tell it to store the VM at?

I don't think you can through Cockpit at this point. You need to either use virsh or Virt-Manager.

@irj said in Anybody using Red Hat satellite?:

@stacksofplates said in Anybody using Red Hat satellite?:

A weakness is Katello is a huge pain to set up. I literally used forklift to get a Vagrant box up and then used that Vagrant box as a long living VM.

We had Red Hat come out and setup Satellite for us.

Cheater :winking_face: yeah I can see why you would want that. I wouldnt want to do that myself in prod without someone there

@ccwtech said in Manage KVM through Cockpit:

@Obsolesce The file is on a USB Drive if that matters.

The ISO might need to have the correct SELinux context. Try copying it to your /var/lib/libvirt/images directory and see if it lets you install that way.

@ccwtech said in Manage KVM through Cockpit:

@stacksofplates said in Manage KVM through Cockpit:

@ccwtech said in Manage KVM through Cockpit:

I think I have it figured out but don't know how to actually implement it. I'm running Fedora Server 28 Headless - so I have the ISO file for the drivers in /usr/share/virtio-win

I think I just need to mount the ISO for the VM but not sure how to do that.

Easiest for a first timer is virt-manager. Just click the IDE CDROM device and then click connect. You can pick your ISO from the browser.

Can you use virt-manager on a headless install?

Yeah. You can either X11 forward from the remote system or use a local install and SSH/HTTP/HTTPS for the QEMU connection.

Sadly virt-manager is the easiest for some things like attaching ISOs. The domain has to be running to attach an ISO however you can't hotplug an IDE device. So you're left with editing the XML for the domain. It's not hard just virsh edit vmname but still annoying.

@obsolesce said in Fedora 28 Server - Linux 101 - How do you partition your drives:

The only time I don't let / use up all my drive space is (usually every time) when I know I will have important data or a need for an amount of storage to be separate from the OS. I like to keep the OS stateless, and the stateful data separate, when possible or when it makes sense.

This has already saved me a few times, when having to reload or restore the OS while keeping the /data or /home partitions intact. All cases were when using LVM.

One could say "well, backups", but you know what's faster? Not having to restore from backups because you made a simple decision when installing the OS that has no negative consequence, only potential benefits.

Yeah we have logs and data on separate volumes from the OS. Saves you if the logs take off or if you have more data than expected.

Hese's the link. She said it was planned for this year.

https://community.spiceworks.com/topic/2090360-unitrends-backup-replication-to-kvm-google-cloud

@scottalanmiller said in KVM Backing and Support:

@stacksofplates said in KVM Backing and Support:

@storageninja said in KVM Backing and Support:

@stacksofplates said in KVM Backing and Support:

There are merits to both sides. For example we do have a lot "backed up" in Git. Things like DHCP servers, DNS servers, web servers, etc that don't have stateful data are stored in Git. Then that Git server is obviously backed up. And you get a little extra redundancy since Git is distributed by nature. We do "agent" based but only because everything is under some type of CM. So it's easy to just make sure that system has the agent's backup role applied to it and that's done automatically.

But I can also see how small shops with not much help would to spend a small amount of money and be able to do agentless with not much extra work.

The other thing that I think people loose track of in their "war on state sprawl" is that most companies don't control the code they have deployed. 75% of code in large enterprises they don't own. You can do platform migrations to open source, and hire developers to do this but if the alternative is $1000 a host for a Veeam license you will get laughed out of the meeting by anyone who's done an ERP migration.

Realistically the easiest way to get rid of backup headaches is to make them someone else's problem. Use SaaS applications, and if it makes sense use SaaS Backup products (Spanning). If the person who owns the code is delivering it, ideally they should be able to achieve enough scale to make custom protection work, or aggregate enough demand to have more leverage with the backup vendors they purchase from.

10000%. If you have the option to use someone else's systems, do it. However while most things in our group are open source, our ERP is all tied into Oracle and a lot of that is delivered with APEX.

APEX is just Access for people with deep pockets and no clue.

That was my point. If you don't have a team who knows what they're doing you should be using someone else's.

As much as I like to argue with @scottalanmiller I have to agree that usually agents are easier.

Because the agent based backup meant that to recover the entire guest, I would have to mount a special ISO, it wasn't nearly as straightforward as "restore this backup from 15 minutes ago to Host 2".

That is in no way a requirement of agent based systems. This sounds more like there isn't a reliable way to reproduce a system and the data isn't on a separate volume. Make sure the systems can be rebuilt immediately and you can just reattach the data and be done.

Even with something as simple as ReaR, you define your skeleton volumes you want backed up and include that in your template.

Example (I'll use Ansible since that's what I know):

The template would have this in it:

BACKUP_PROG_INCLUDE=('{{ backup_dirs | join("' '") }}')

You'd have a list (in this case called backup_dirs) that gets iterated over:

backup_dirs:
  - /home/*
  - /data/*
  - /var/www/html/*

That backup_dirs list is specific to each machine when it's created.

The agent based stuff is really simple because it can very easily be specific for each machine and always be specific when the systems are built without any work after the initial set up.

And again, this is only for systems that have data actually stored in them. Stuff like DNS servers can immediately be rebuilt with just definitions like this:

{% for key, value in records.iteritems() %}
{{ key }}   {{ value.type }}   {{ dns_subnet }}.{{ value.last }}
{% endfor %}

and the records dictionary looks like this:

dns_subnet: 192.168.0

records:
  router: { type: A, last: 1 }
  hypervisor1: { type: A, last: 2 }
  hypervisor2: { type: A, last: 3 }
  fileserver: { type: A, last: 4 }

This is specific to BIND (and you'd probably use Unbound anyway, but the logic is still the same) but it gives you awesome flexibility. So now I can run 1000 replicas if I want all with the same data and all changed at the same time, and my SVN system stores the data.

I'll give it a shot when I get to work see if I can figure anything out.

@gjacobse said in Remote Desktop to Fedora 28?:

Yes - I learn. here is the same command - but in just three lines:

sudo dnf install xrdp -y
sudo systemctl start xrdp | sudo systemctl enable xrdp
sudo firewall-cmd --permanent --add-port=3389/tcp | sudo firewall-cmd --reload

You can shorten the second. If you do

system to enable --now xrdp

It will enable and start the service at the same time.

@gjacobse said in Remote Desktop to Fedora 28?:

Yes - I learn. here is the same command - but in just three lines:

sudo dnf install xrdp -y
sudo systemctl start xrdp | sudo systemctl enable xrdp
sudo firewall-cmd --permanent --add-port=3389/tcp | sudo firewall-cmd --reload

Also why are you using a pipe?

This isn't wifi related but a big downside for us is the largest 10 gig switches are only 16 port. For a site with 40 Gb core and 10 Gb everywhere it's a big limitation.

@francesco-provino said in Linux: History:

@stacksofplates said in Linux: History:

you can just do

gedit ~/.bash_history

or if you like the cli

cat ~/.bash_history

Obv only Bash if that's what you're using.

Why conCATenate? Just use LESS.

You can do either or any combination. Mostly just pointing you you don't need the gui.

@travisdh1 said in Fedora: Skype for Linux:

@black3dynamite said in Fedora: Skype for Linux:

@travisdh1 flatpak works well for me on Fedora.

I haven't tried flatpak yet. Guess I'll have to give it a shot.

Flatpak is the Fedora native one. Snap is the Ububtu. Fedora is pushing to have most in the software store be installed with Flatpaks.

delete key.

Sorry I'm of no help to you.

Looks like datamash does this.

Looks like a requirement.

Maybe I missed it. Why aren't you using the guacd provided by dnf?