In questo post creiamo coi mezzi che internet ci offre gratuitamente, un menù digitale, visionabile dal cellulare, e raggiungibile tramite un QA Code.
In tempi di COVID le misure per la sicurezza per le attività (Bar, Pub, Ristoranti etc..) sono aumentate considerevolmente. Una di queste è sicuramente quella che i clienti non possono avere in mano i menù perchè sono superfici che possono trasmettere batteri e virus (es il coronavirus).
Di conseguenza è necessario che il menù sia leggibile e fruibile in digitale, dal proprio smartphone, tablet o pc.
Ci sono già numerose applicazioni e servizi web che vi personalizzano e gestiscono il vostro menù, che lo rendono aggiornabile e carino anche graficamente parlando.
Però è possibile avere un prodotto carino, personalizzabile e aggiornabile real time gratis, grazie a Google Sites e I Generatori di QR Code Online disponibili (QUI uno funzionante).
I prerequisiti sono solo 1: avere un account Gmail/Google (base) ed avere un po’ di dimestichezza con gli editor di testo e immagini on-line.
Ma passiamo subito all’opera.
Aprire (o registrare) l’account GMAIL;
Dal menù a puntini in alto a destra accedere al proprio Google Drive
3. Cliccare su NUOVO
4. poi ‘Altro’ e infine su Google Sites
La Creazione del Menù/Sito
Google Sites propone anche una galleria di modelli, fra i quali un ‘Ristorante’, molto completo. Potete inserire una descrizione, attivare una metodologia di contatto, inserire le foto ed ovviamente comporre il menù.
Oppure potete iniziare a vostro piacimento da un modello vuoto e comporlo come meglio volete con immagini, sezioni, testi etc…
Mettiamo che aprissi un ristorante e lo chiamassi ‘Widenet‘
Posso selezionare una immagine da caricare come sfondo (posso caricarne una dal mio PC, internet magari precedentemente selezionata da internet, oppure selezionarne una da quelle proposte).
Sulla destra è presente un menù per inserire nuovi elementi, immagini, cambiare il tema etc…
Nel mio caso ho inserito delle caselle di testo, una per ogni tipologia di portata come Antipasti, Primi Piatti, Secondi etc…
(Nomi e Prezzi inseriti totalmente a caso 🙂 )
Come vedete ogni casella ha il suo editor per il carattere, elenchi numerati o puntati, allineamento etc…
Come vedete ho proprio messo il tutto un po’ velocemente. Ma con un po’ più di tempo e capacità grafiche (io non ne ho) è possibile elaborare qualcosa di bello e dettagliato. Per esempio potete inserire tutti gli ingredienti dei piatti, gli allergeni, traduzioni in tutte le lingue che ritenete opportuno etc…
A questo punto non vi resta che publicarlo.
Cliccate su ‘Publica’ in alto a destra
e vi apparirà un pop-up dove potete inserire un nome, che funzionerà anche come nome di dominio assoluto del sito tramite l’URL che vi verrà proposta:
Fra le altre opzioni interessanti ci sono quelle di:
– avere un URL personalizzato (www.ilm iodominio.it) – ma a pagamento e con una procedura separata;
– la gestione di chi può visualizzare il sito (da lasciare su PUBBLICA perchè deve essere visibile a tutti ma non modificabile);
– richiedere ai motori di ricerca di non indicizzare il vostro sito (a vostra discrezione, io consiglierei di fare un lavoro carino e di indicizzarlo). A questo punto ri-cliccate su PUBBLICA in basso a destra.
Zabbix is one of the our favourite open source monitoring system. It offers dozens of functions, models, templates dedicated to the most importants vendrors (visit Zabbix Share).
What’s New in Zabbix 5.0 LTS Zabbix 5.0 LTS release comes with significant improvements in usability, security, and integrity.
Here is just a shortlist of the most important functionality included in Zabbix 5.0 LTS.
You choose: deploy on-premise or in the cloud Zabbix is a Free and Open Source monitoring solution that can be deployed everywhere depending on your needs!
In addition to existing official packages and appliances, Zabbix 5.0 now also caters to the following platforms: SUSE Linux Enterprise Server 15, Debian 10, Ubuntu 20.04, Raspbian 10, Mac OS/X, RHEL 8, CentOS 8, MSI for Windows Agent.
See all available platforms in Downloads
Zabbix introduces a new set of out-of-the-box integrations with industry-standard cloud providers:
Google Cloud Platform
SAML authentication for single sign-on SAML is used to provide a single point of authentication at a secure identity provider, meaning that user credentials never leave the firewall boundary, and then SAML is used to assert the identity to Zabbix and other applications. Support of SAML allows to have out-of-the-box integration of Zabbix with various on-premise and cloud identity providers like Microsoft ADFS, OpenAM, SecurAuth, Okta, Auth0 and many others.
Secure and reliable monitoring Zabbix 5.0 introduces significant improvements for much more secure monitoring:
Support of HTTP Proxy for webhooks that allows to make connections from Zabbix Server to external alerting and ITSM systems more secure and controlled
Support of blacklists and whitelists for metrics on agent-side
Configurable ciphers for all Zabbix components to avoid using of non-secure ciphers for TLS connections
Support of encrypted connections to MySQL and PostgreSQL backends
Strong SHA256 for keeping hashes of user passwords
Keep your secrets secure Zabbix 5.0 supports secret user macros for keeping any sensitive information like passwords and API tokens that you do not want to be exposed to end-users.
Scalability and performance Zabbix 5.0 supports optional compression of collected data for TimescaleDB. In addition to general TimescaleDB advantages (automatic partitioning, performance and scalability) it also helps to even more improve performance and lower storage costs.
Zabbix UI is also improved to support monitoring and management of millions of monitored devices.
Next generation Zabbix Agent got official support The new agent offers a wide range of new capabilities and advanced monitoring functions for Linux and Windows:
Written in Golang
Plugin framework for monitoring of various services and applications
Ability to maintain state between checks (for example, keeping persistent DB connections)
Support of trapping
Built-in scheduler to support flexible time intervals
Efficient network usage through bulk data transfer
Support of persistent storage of collected data
Drop-in replacement of existing agents on Linux and Windows
NB! Existing Zabbix agent will still be supported.
Next generation Zabbix Agent got official support Monitoring that is easy to use and manage Zabbix 5.0 got tons of usability and automation improvements that help:
Threading for email notifications generated by the same event
New preprocessing operation Replace, new operator for JSONPath
Ability to unacknowledge event
Support of message templates for media types for straight forward configuration of notifications
Ability to test new and existing metrics from UI
Support of mass update of user macros
SNMP settings moved to host interface level for more simple templates and easier management
Host and metric availability monitoring using function nodata() respects availability of proxies
Monitoring that is easy to use and manage
Flexibility to monitor anything you want Zabbix 5.0 extended functionality to make it more flexible:
Triggers support operations with text data
Support of host macros for host prototypes
Support of Float64 datatype
Support of override for low level discovery (LLD) helps to create much smarter templates
Flexibility to monitor anything you want
Automation and discovery Automation is an essential part of Zabbix. Zabbix 5.0 brings it forward with support of:
Discovery of Windows performance counters
Discovery of JMX counters
Better ODBC monitoring with ability to configure all options for each metric individually
Advanced visualization Presenting data in a human readable way is critical for operations. Zabbix 5.0 helps to make it even better by introducing:
New layout of Zabbix UI optimized for wide screens
A new view (Monitoring->Hosts) for displaying a list of monitored devices with advanced filtering options
Support of filtering by event tags for some dashboard widgets
Ability to copy dashboard graphs as pictures
Support of UI modules to extend functionality of Zabbix
Faster creation of dashboards thanks to ability to copy widgets
Improved consistency of map labels
Test item from UI In previous Zabbix versions, it was difficult to tell if a newly-configured item was configured correctly or not. For that you needed to wait until the item tried to gather some data.
In the new version it is possible to test the item (template item, item prototype, low-level discovery rule) from the user interface even before saving and, if configured correctly, get a real value in return.
Item testing is not supported for active items and some simple checks (icmpping*, vmware.* items).
To test the item, click on the Test button at the bottom of the item configuration form.
Built-in integrations with ITSM systems Zabbix 5.0 introduces a new set of out-of-the-box integrations with industry-standard cloud-based and on-premise ITSM systems.
Official webhook Coding Guideline was introduced to set standard and simplify creation of webhook based integrations.
Adjust Zabbix to your needs, contribute! Make your template, plugin or a webhook included into the official Zabbix distribution by following these three steps:
Sign Zabbix Contributor Agreement (ZCA) zabbix.com/developers Make Zabbix Pull Request https://git.zabbix.com Zabbix Dev Team will review and accept if everything is fine Congratulations! Your solution is officially supported and thousands of Zabbix users are thankful for your effort!
More newly developed and improved features of Zabbix 5.0 LTS
Increased size of acknowledge messages from 255 to 4096 characters
Added support of LIBSSH to support newer platforms like RHEL 8
Support of Elasticsearch 7.x (7.4, 7.6)
Latest data displays data if filter is not set
Increased zabbix_sender time resolution to nanoseconds
Monitoring->Latest data: show data if filter is empty
Do not log system.run for local use
Increased size of item key from 255 to 2048 characters
Ability to flush SNMP cache, SNMPv3 context changes
Faster hash function for internal operations
Documented how to do filtering for vmware.event monitoring
Improved consistency of map labels
Filter by individual severities for Monitoring→Problems
Ability to use user macros for IPMI user name and password
Remote monitoring of versions of Zabbix components
Added filter for discovery rules
New API method to get auditlog
Removed legacy to build a better product faster
No support of Internet Explorer 11
Dropped support of IBM DB2
mbedTLS (former polarSSL) is no longer supported for encryption. Only OpenSSL and GnuTSL libraries
Minimum supported version for PHP is now 7.2: safer and more strict code And more! For a complete list of new features check out the Release notes. Release Notes.
Today we will see how to Install JFrog Artifactory on Ubuntu 18.04/16.04. JFrog Artifactory is the world’s most advanced repository manager designed to integrate with the majority of continuous integration and delivery tools. With JFrog Artifactory, delivering an end to end automated solution with artifacts tracking from development to production becomes a reality.
Artifactory is mostly used by build tools such as Maven, Apache Ant, and Gradle to store respective artifacts in its local repository to be consumption by other applications and tools.
Install JFrog Artifactory on Ubuntu
The easiest way of installing and running Artifactory on Ubuntu 18.04/16,04 is by using Docker. The process is straightforward without dependency/permission hurdles. You just install Docker, download Artifactory image and spin a container.
Step 1: Install Docker Engine
Install Docker. For a quick start, here is the process.
Install packages to allow apt to use a repository over HTTPS:
If you would like to use Docker as a non-root user, you should now consider adding your user to the “docker” group with something like:
sudo usermod -aG docker $USER
Run the command below to see a version of docker installed.
$ docker version
API version: 1.39
Go version: go1.10.8
Git commit: e8ff056
Built: Thu Apr 11 04:43:57 2019
Server: Docker Engine - Community
API version: 1.39 (minimum version 1.12)
Go version: go1.10.8
Git commit: e8ff056
Built: Thu Apr 11 04:10:53 2019
Step 2: Download JFrog Artifactory Docker image
There are different editions of JFrog Artifactory available, check the Comparison Matrix. If you’re not sure, install the OSS (Open Source Software) version. For more features, you can consider the Pro.
Pull the latest Docker image of JFrog Artifactory.
$ docker images
REPOSITORY TAG IMAGE ID CREATED SIZE
docker.bintray.io/jfrog/artifactory-cpp-ce latest 24d943a892ac 43 hours ago 582MB
docker.bintray.io/jfrog/artifactory-oss latest 58d49856785f 43 hours ago 582MB
Step 3: Create Data Directory
Create data directory on host system to ensure data used on container is persistent.
Widenet is VCP Certified for VMware Products.
In many Article, we talked about Tips & tricks, or to solve problems, like here, or here. Now we will talking about a big news from VMware.
vSphere 6.7, released today, includes an update to both its hypervisor (ESXi 6.7) and management console (vCenter Server 6.7). This release shows that VMware Inc. is not content to let its hypervisor become a commodity, and that it’s possible to make incremental, evolutionary changes to a proven product and, moreover, that VMware is still making substantial investments in its hypervisor. The vSphere 6.7 beta, though NDA-constrained, has been available to the public since October 2017. Despite the fact that a lot of new features were baked into the 6.5 release, this release does make some nice incremental changes. Following are some of the most important changes included with vSphere 6.7.
An important hardware caveat to be aware of is VMware has released an HCL for vSphere 6.7 that excludes some older, yet popular CPUs. If you’re thinking about running this release on an older system for development or testing first before placing it into production on your newer servers, make sure to check the HCL to ensure compatibility.
Single Reboot Upgrade
vSphere upgrades can now be completed with one single reboot. Prior to vSphere 6.7, major version upgrades took quite a while (although they could be done without disruption by transferring workloads by using the Distributed Resource Scheduler [DRS]). vSphere 6.7, on the other hand, allows you to do a “quick boot” where it loads vSphere ESXi without restarting the hardware because it only restarts the kernel. This feature is only available with platforms and drivers that are on the Quick Boot whitelist, which is currently quite limited.
VMware Configuration Maximum Tool
The most visible configuration maximum change in vSphere 6.7 is the number of devices that can be attached to a host. VMware has increased some of the other maximums.
vSphere 6.5 eliminated the vSphere Client that ran natively on Windows (also known as the C# Client or Thin Client) in favor of the vSphere Web Client, which was Flash-based. Also introduced in version 6.5 was the vSphere Client, which replaced Flash with HTML5. vSphere 6.7 further extends the capabilities of the vSphere Client and will eventually replace the vSphere Web Client. It looks like the vSphere Client can do about 90 percent that the vSphere Web Client can do. In vSphere 6.5, VMware had a list of the functionalities not yet supported in the vSphere Client; hopefully the company will do the same for vSphere 6.7. Figure 1 shows the main menu of the vSphere Web Client, and Figure 2 shows the main vSphere Client menu. Although the new client looks cleaner, and does seem more responsive than the vSphere Web Client, the location of some items has changed and some workflows will have to be adjusted accordingly with these changes. I wrote an article on the vSphere Client when it first came out that explains why VMware is switching to an HTML5-based client.
vCenter Server Appliance
Now that the vCenter Server Appliance (VCSA) is functionally equivalent to the Windows-based vCenter Server, it would take a lot to convince me to use the Windows-based one instead of VCSA. Overall, I have found that the VCSA embedded database (PostgreSQL) performs great. Furthermore, the VCSA is very easy to update, and the Linux OS (Photon OS) is rock solid. As a side note, the VCSA can easily be monitored using vimtop (be sure to read my recent articles on using vimtop). You can also read my article about migrating from a Windows-based vCenter Server to a VCSA, as well as another article on using the built-in VCSA backup tool. The built-in backup tool in vSphere 6.7 offers more scheduling options for its VCSA backup tool than in vSphere 6.5. The Backup Scheduler tool (Figure 3) can be accessed from the vCenter Server Appliance Management Interface (VAMI). VMware is also stating that there are “phenomenal” performance improvements in vCenter operations per second, in reduction of memory usage and DRS-related operations.
Suspend and Resume of vGPU Workloads
vGPU allows you to carve up a physical GPU into multiple virtual GPUs that can be used by VMs. Although vGPUs were introduced with vSphere 6.0, the VMs that used vGPUs there were limited in what you could do with a VM that was using a vGPU. vSphere 6.7, on the other hand, removes some of these barriers, and now you can suspend and resume a vGPU-enabled VM.
For quite some time vSphere has had the ability to mask off CPU features so that VMs that were running on systems with newer CPUs could be vMotion to servers with older CPUs. This is called Enhanced vMotion Compatibility, or EVC. In vSphere 6.7 VMware has extended this capability to allow you to do this on a per-VM, rather than on an ESXi-host basis. This means that if you have VMs that you want to take advantage of CPU-specific features, and are willing to limit those VMs to CPUs that only have those features in your cluster, you can configure them to do so.
A per-VM EVC is set from the vSphere client by selecting a VM, going to the Configure tab and selecting Edit (Figure 4).
I’ve been a fan of using instant clones with virtual desktops—they’ve proven to be a big space saver, to use only a fraction of the disk resources compared to a full clone, and to allow VMs to be provisioned in seconds from a parent image. With vSphere 6.7, VMware has exposed the APIs that can be used to create instant clones. It looks like a straightforward process and I suspect that many people will figure out some very interesting ways to use the instant clone API.
ESXi Quick Boot
vSphere 6.7 introduces the Quick Boot feature, which allows a system to reboot in less than two minutes as it does not re-initialize the physical server BIOS. This can speed up operations that require an ESXi system to be rebooted; however, Quick Boot is only supported on certain systems and does not work with systems that have ESXi Secure Boot enabled.
Figure 5 shows two hosts, one with Quick Boot enabled and another without it enabled. By default, Quick Boot is enabled if the system supports it.
Persistent Memory (PMem) Devices
vSphere 6.7 now supports the next generation of storage devices that use persistent DRAM memory, known as non-volatile dual in-line memory module (NVDIMM) devices. This technology is still in its infancy, but applications that require the lowest possible latency regardless of the cost will find this feature invaluable. PMem is presented to vSphere as either as vPMemDisk, which is treated somewhat like a datastore, or as a virtual NVDIMM (vNVDIMM), which is presented directly to guest OSes that can use NVDIMM devices.
Virtual Hardware Version 14
Virtual hardware is the abstract version of physical hardware to a virtual machine or, in essence, a virtual motherboard. As physical hardware supports more features, VMware builds new virtual hardware accordingly to emulate the physical version. vSphere 6.7 comes with a new virtual hardware, version 14. Version 14 adds support for NVDIMM, as well as Trusted Platform Module (TPM), Microsoft Virtual-based Security (VBS) and I/O Memory Management.
VMFS3 datastores have been around for a long time, but VMware is now phasing them out. To assist with this transition, vSphere 6.7 automatically upgrades VMFS3 datastores to VMFS5 when they’re mounted. If you want to upgrade VMFS5 datastores to VMFS6 datastores, you’ll need to upgrade the datastore with vSphere Storage vMotion because an in-place upgrade of a VMFS5 to VMFS6 datastore isn’t possible.
As a side note, vSphere 6.7 supports VMFS5 and VMFS6; however, vSphere 6.0 and earlier systems only support VMFS5 datastores. As such, if you have an environment that contains vSphere 6.0 or earlier systems, you’ll want to only use VMFS6 datastores on systems that won’t be accessed by them.
Upgrading to vCenter Server 6.7
A specific order must be used when upgrading to vSphere 6.7. Check the documentation for the latest order and caveats, but the basic procedure can be carried out by first upgrading the Platform Service Controller (PSC), then upgrading vCenter Server and, last, updating the ESXi hosts.
Because upgrading directly from vSphere 5.5 to 6.7 isn’t supported, you’ll need to first upgrade from vSphere 5.5 to vSphere 6.5, and then finally to vSphere 6.7. It needs to be noted that an ESXi 5.5 host cannot be managed by VCSA 6.7. On the contrary, upgrading from vSphere 6.0 to 6.7 is supported. If you’re still running a window-based vCenter Server rather than a VCSA, VMware does offer a tool to assist you in the migration; be sure to read my article on using this tool.
Upgrading to ESXi 6.7
As mentioned earlier, ESXi 6.5 doesn’t support all the CPUs that ESXi 6.0 does, so be sure to check the HCL to unsure that your system is supported. Roughly speaking, what you’ll typically find supported, at the minimum, is a 2 core CPUs that were released after September 2006 and have NX/XD enabled. You can use the VMware Update Manager (VUM) to do an orchestrated automated upgrade. Alternatively, you can manually update the ESXi systems using an ISO image or esxcli commands or, if you use stateless host, you can use vSphere Auto-Deploy to update your servers. To see how to update an ESXi system using esxcli commands, be sure to read my article.
If I’m forced to pick one single standout feature in vSphere 6.7, it would have to be the instant clone API. I see this feature as a great enabler for the VMware ecosystem and VMware developers because the ability to spawn hundreds of identical VMs that only use a small amount of space in minutes has some mind-boggling use cases. However, with great power comes greater responsibility, and it will be interesting to watch the development of tools to manage and orchestrate these VMs over time.
Yes, instant clones is the gee-wiz feature in this release, but the rest of the improvements in this release prove that the hypervisor has room for evolutionary growth—and that VMware is serious in maintaining its leadership position in this regard.
Necessary cookies are absolutely essential for the website to function properly. This category only includes cookies that ensures basic functionalities and security features of the website. These cookies do not store any personal information.
Any cookies that may not be particularly necessary for the website to function and is used specifically to collect user personal data via analytics, ads, other embedded contents are termed as non-necessary cookies. It is mandatory to procure user consent prior to running these cookies on your website.