I thought I’d upgrade my Ubuntu XPS13 from Groovy-whatever-it-was to Hirsute Hippo (21.04 I guess?). It moved me to use Wayland by default. Some bits feel OK – somehow the visual feedback from app launching seems better (it may not be any quicker) …
But …
The alt-tab window switching thing often stops working – this has happened a number of times, across reboots.
Apps appear to be running in the UI, when they’re not.
I’ve had the desktop icons randomly display on top of a full screen video (possibly Amazon Prime Video?)
I’ve had the launcher buttons just stop working
I can’t use a clipboard manager (so no copy+paste buffers to cycle through)
So you’ve created an ElasticSearch 7 standalone cluster, in Azure, and wish to use the Azure Repository plugin to handle backups.
You’re also conscious about not exposing storage accounts on public IP addresses (if they need not be)….
So, given you’ve created a storage account within Azure called e.g. mysimplestorage and given it a private-link connection to the same virtual network your ElasticSearch Servers will be on … you should find it has a hostname like mysimplestorage.blob.core.windows.net (see the ‘Endpoints’ “tab” within the storage account. That ‘mysimplestorage‘ is needed below.
What else needs doing ?
Well,
a) you don’t want proxy settings in your elasticsearch.yml file (azure.client.default.proxy.host: …. and other things)
b) You probably do want to create a Managed Identity to attach to your virtual machines, which gives them access to to the storage account (I called mine ‘elasticsearch7’ as I have no imagination). Assign that role ‘owner’ for the given storage account (perhaps there is a finer grained permission?)
c) When creating new VMs for the cluster, you can use :
az vm identity assign -g MyResourceGroup -n NewServerName –identities elasticsearch7
d) Edit the Storage Account’s access control list, and add the role in
e) install the azure repository plugin on your elasticsearch nodes
At this point, restart all your ElasticSearch nodes (for me they don’t seem to pickup keystore settings until a restart) and then go into Kibana and configure the backup routine.
I’ve been using ‘varnish’ for ages for caching webcontent (e.g. wordpress sites). Then I needed https support (cue Apache or haproxy) …. then I needed http 2.0 support ….
I’ve finally bothered upgrading off Varnish 3 to Varnish 6, and adding in ‘hitch’ (and http/2.0 / h2 support).
Random configuration snippets … this is from using Debian.