- Go to https://store.rg-adguard.net.
- Search for the HEVC Video Extensions from Device Manufacturer (
Microsoft.HEVCVideoExtension
) app by entering the following store URL.https://www.microsoft.com/en-us/p/hevc-video-extensions-from-device-manufacturer/9n4wgh0z6vhq
- Do not use the normal HEVC Video Extensions app URL, because that can't play HEVC videos in Windows Media Player for some inscrutable reason.
- Download the AppxBundle file.
- You may have to right click › Save Link As because the URL scheme is http, not https, if your browser is set to enforce HTTPS-only mode.
- If it tries to save as a filename that's just a GUID, you may copy the correct .AppxBundle filename and save it as that instead.
#!/bin/bash | |
# Copyright 2016, Rackspace US, Inc. | |
# | |
# Licensed under the Apache License, Version 2.0 (the "License"); | |
# you may not use this file except in compliance with the License. | |
# You may obtain a copy of the License at | |
# | |
# http://www.apache.org/licenses/LICENSE-2.0 | |
# | |
# Unless required by applicable law or agreed to in writing, software |
Automating things in software development is more than useful and using Ansible is one way to automate software provisioning, configuration management, and application deployment. Normally you would install Ansible to your control node just like any other application but an alternate strategy is to deploy Ansible inside a standalone Docker image. But why would you do that? This approach has benefits to i.a. operational processes.
Although Ansible does not require installation of any agents within managed nodes, the environment where Ansible is installed is not so simple to setup. In control node it requires specific Python libraries and their system dependencies. So instead of using package manager to install Ansible and it’s dependencies we just pull a Docker image.
By creating an Ansible Docker image you get the Ansible version you want and isolate all of the required dependencies from the host machine which potentially might break things in other area
This guide describes how to bootstrap new Production Core OS Cluster as High Availability Service in a 15 minutes with using etcd2, Fleet, Flannel, Confd, Nginx Balancer and Docker.
Then, I used the actual server range... Hetzner assigns a /64 IPv6 range. We have to tell Docker the network new containers are going to have, and we also have to specify the network ranges new networks will have (docker compose creates them). | |
If the server has been assigned the `2001:0db8:2a01:4f8::/64` range, that means it can control all the addresses from `2001:0db8:2a01:04f8:0000:0000:0000:0000` to `2001:0db8:2a01:04f8:ffff:ffff:ffff:ffff`. That's... a lot of addresses. The server is using `2001:0db8:2a01:4f8::1` (or `2001:0db8:2a01:04f8:0000:0000:0000:0001`). | |
Now, each docker network needs at least an /80 range so that it can generate ip addresses from mac addresses. | |
So what I'm going to do is: | |
1. Set `2001:0db8:2a01:4f8:1000::/68` as the default network range. It means the default network will have addresses from `2001:0db8:2a01:04f8:1000:0000:0000:0000` to `2001:0db8:2a01:04f8:1fff:ffff:ffff:ffff` | |
2. Add a default address pool that's `2001:0db8:2a01:4f8:2000::/68`, but so that new networks take /8 |
#!/bin/bash | |
qemu-system-x86_64 -enable-kvm -m 4096 -smp $(nproc) -cpu host -device ac97 -audiodev alsa,id=snd0,out.buffer-length=500000,out.period-length=726 -usb -device usb-tablet -device virtio-keyboard-pci -net nic -net user -cdrom distro.iso -device virtio-vga-gl -display gtk,gl=on,grab-on-hover=on -hda disk.qcow2 -bios /usr/share/edk2/ovmf/OVMF_CODE.fd |
https://1337x.to/ | |
https://www.torrentfunk.com/ | |
http://www.torrentbit.net/ | |
https://www.torlock.com/ | |
https://torrentproject.se/ |
#!/bin/bash | |
set -x | |
fsid="$1" | |
cephadm rm-cluster --fsid $fsid --force | |
source /etc/os-release | |
sudo systemctl stop tripleo_\* | |
sudo systemctl stop ceph\* | |
sudo pcs cluster destroy | |
if [ $VERSION_ID == "7" ]; then | |
sudo docker ps -a -q | xargs docker rm -f |
Are you let down when you saw there is no guide to use Windows Server 2016 under *nix environments? I really loved Microsoft when I heard they are working on Windows containers, but when this week has arrived, it was sad to see that installation requirements were Windows and HyperV. But actually it is not. You just have to modify the VHD file a bit with nicer tools and execute the already available script in the downloaded VM. I will assume you are running a decent version of Linux and accepted EULA and all the legal stuff that I do not care.
$ sudo apt-get install qemu-kvm virt-manager // or virtualbox, but we need qemu-kvm for image manipulation
$ sudo apt-get install qemu-utils libguestfs-tools // image manipulation tools