Close

Free DNS providers

Google 8.8.8.8: Private and unfiltered. Most popular option.
CloudFlare 1.1.1.1: Private and unfiltered. New player.
Quad9 9.9.9.9: Private and security aware. New player that blocks access to malicious domains.
OpenDNS 208.67.222.222: Old player that blocks malicious domains and offers the option to block adult content.
Norton DNS 199.85.126.20: Old player that blocks malicious domains and is integrated with their Antivirus.
CleanBrowsing 185.228.168.168: Private and security aware. New player that blocks access to adult content.
Yandex DNS 77.88.8.7: Old player that blocks malicious domains. Very popular in Russia.
Comodo DNS 8.26.56.26: Old player that blocks malicious domains.

Advertisements

Virtualizing pfSense on Proxmox (4 and 5)

Assumptions

  • Proxmox host is up and running
  • Host has at least two network interfaces available for WAN and LAN.
  • you have already upload pfSense image to the host

Basic Proxmox networking

In order to virtualize pfSense we first need to create two Linux Bridges on Proxmox, which will be used for LAN and WAN. Select your host from the server view, navigate to System > Network. We will be using eth1 and eth2 interfaces for pfSense, while eth0 is for Proxmox management.

Screen Shot 2017-06-17 at 23.19.20.png

Click on create and select Linux Bridge. Under Bridge ports enter eth1.

Screen Shot 2017-06-17 at 23.19.59.png

Repeat the process to add another Linux Bridge, this time add eth2 under Bridge ports.

Screen Shot 2017-06-17 at 23.20.13.png

Proxmox Networking should now display two Linux bridges like on the following screenshot. WARNING: Proxmox requires reboot if the interfaces are not marked Active.

Screen Shot 2017-06-17 at 23.23.59.png

Creating pfSense virtual machine

After creating WAN and LAN Linux bridges, now we proceed to create a new virtual machine. Click on Create VM from the top right section and new virtual machine wizard will appear. Under General tab, add a name to your pfSense VM.

Screen Shot 2017-06-17 at 23.28.02.png

Under OS tab select Other OS types and click next.

Screen Shot 2017-06-17 at 23.28.08.png

On CD/DVD tab select local storage and under ISO image find the previously uploaded pfSense ISO.

Screen Shot 2017-06-17 at 23.28.15.png

On the next tab, select VirtIO under Bus/Device and enter disk size you need.

Screen Shot 2017-06-17 at 23.28.31.png

On the CPU tab select a single socket and add one or more cores. Confirm CPU type is Default (kvm64).

Screen Shot 2017-06-17 at 23.28.56.png

Under Memory tab add at least 1024 MB. Use fixed size memory.

Screen Shot 2017-06-17 at 23.29.17.png

On the Network tab select Bridged mode and vmbr1. Make sure VirtIO (paravirtualized) is selected under Model.

Screen Shot 2017-06-17 at 23.29.29.png

Finally confirm the settings and wait for the VM to be created. Select your newly created virtual machine from the server view sidebar.

Screen Shot 2017-06-17 at 23.29.46.png

While the pfSense virtual machine is selected, click on Hardware settings and add another network device. Under Bridge enter vmbr2 and select VirtIO (paravirtualized) under Model.

Screen Shot 2017-06-30 at 18.23.47.png

Confirm your virtual machine has two network interfaces now.

Screen Shot 2017-06-17 at 23.30.05.png

Starting and configuring the pfSense virtual machine

After creating a new virtual machine and adding network interfaces, it’s time to start the virtual machine. If everything was done correctly, you can see pfSense booting up from the Console window

Screen Shot 2017-06-17 at 23.30.32.png

pfSense will prompt you to select boot mode, press I to launch the installer.

Screen Shot 2017-06-17 at 23.31.06.png

When pfSense setup boots up, follow the installation steps as you would on a physical device. Simply run Quick/Easy setup and wait for it to complete. When prompted, select standard kernel. Click reboot to complete the installation. Make sure you remove the .ISO from the virtual CD/DVD media.

Screen Shot 2017-06-17 at 23.41.38.png

After pfSense virtual machine reboots you will be greeted by interfaces assignment wizard. We will not set be setting up VLAN’s now, so press N and confirm

Screen Shot 2017-06-17 at 23.44.04.png

On the following steps assign the WAN and LAN interfaces. For the purpose of this guide, we have assigned vtnet0 to WAN and vtnet1 to LAN.

Screen Shot 2017-06-17 at 23.44.18.png

After interfaces have been assigned, pfSense will complete the boot.

Screen Shot 2017-06-18 at 00.01.41.png

Configuring pfSense to work with Proxmox VirtIO

After the pfSense installation and interfaces assignment is complete, connect to the assigned LAN port from another computer.

WARNING: because the hardware checksum offload is not yet disabled, accessing pfSense WebGUI might be sluggish. This is NORMAL and is fixed in the following step.

To disable hardware checksum offload, navigate under System > Advanced and select Networking tab. Under Networking Interfaces section check the Disable hardware checksum offload and click save. Reboot will be required after this step.

Screen Shot 2017-06-30 at 18.51.25.png

Congratulations, the pfSense virtual machine installation and configuration on Proxmox is now complete.

 

Source: https://doc.pfsense.org/index.php/Virtualizing_pfSense_on_Proxmox

Proxmox VE differential backups

Source: https://ayufan.eu/projects/proxmox-ve-differential-backups/

Proxmox VE is a complete virtualization management solution for servers. You can virtualize even the most demanding application workloads running on Linux and Windows Servers. Checkout their page: proxmox.com

Due to lack of better backup functionality I prepared patches to support differential backups in Proxmox VE. These patches are in use for over a year.

Currently supported versions are 3.4, 4.1, 4.2, 4.3, 4.4, 5.0.

What are differential backups?

According to Wikipedia:

A differential backup is a type of data backup that preserves data saving only the difference in the data since the last full backup. (…) Another advantage, at least as compared to the incremental backup method of data backup, is that at data restoration time, at most two backup media are ever needed to restore all the data. This simplifies data restores as well as increases the likelihood of shortening data restoration time.

What my patches do?

My patches extends vzdump, xdelta3 and Web-GUI support. And yes, these patches fully support OpenVZ and KVM.

System administrator can use one additional parameter in Backup Jobs (Datacenter -> Backup -> Add/Edit) the Full Backup Every:

  • By default this value is set to 0. Which simply means: use old behavior (always create full backups).
  • But if you specify value larger than 0, for example 7. It will instruct the vzdump to create full backup once a week and use differentials for the rest.

Please consider the following example:

    vzdump 101 --remove 0 --mode snapshot --compress lzo --storage local --node hvm --fullbackup 4

It will create full backup of VM101 every 4 days, compressed using lzo, stored on local storage.

How to install?

There are three files:

    c760d7481beae8dba3c62f1d95c6fbde  pve-2.2-diff-backup-addon
    42c1a0f34eca9ac23de83523db00f6c5  pve-2.3-diff-backup-addon
    1292670afa84914aac4ebda59d2a7122  pve-3.0-diff-backup-addon
    cd68c203bb1804105a3b4acd52382f6d  pve-3.1-diff-backup-addon
    67fb4d2b397759fb83066ae93cc07b78  pve-3.2-diff-backup-addon
    3e095bd0ed5744a545016018e235fa27  pve-3.3-diff-backup-addon
    350ed7844a5802ca114a6b60e0b013dc  pve-3.4-diff-backup-addon
    e33ef0b546fb16baacc4baed57af20d2  pve-3.4-14-diff-backup-addon
    1657dbc46d9f8b379896a9c0a7dffc3e  pve-4.0-diff-backup-addon
    e5701606733fb10dc117ff2b008da11b  pve-4.1-diff-backup-addon
    9fd8b3cb99283e55b00d694ce633b723  pve-4.1-22-diff-backup-addon
    300b07f7837200b9cc281aff06105991  pve-4.2-diff-backup-addon
    05c8520f87443a8902faa3b24d25735f  pve-4.2-17-diff-backup-addon
    c9fc4aeb2e42d1d78f54c8e7b007fc3d  pve-4.3-diff-backup-addon
    3991a5773e1d85503513889eaf04910c  pve-4.4-diff-backup-addon
    6646d0bc79a70beeca482dcf5354d021  pve-4.4-13-diff-backup-addon
    cc07c340b4dbfcf00e9d216a2f8f8466  pve-5.0-diff-backup-addon

The installation procedure is fairly simple:

  1. Logged as root download:For PVE 2.2 (deprecated):
    wget http://ayufan.eu/projects/proxmox-ve-differential-backups/pve-2.2-diff-backup-addon
    

    For PVE 2.3 (deprecated):

    wget http://ayufan.eu/projects/proxmox-ve-differential-backups/pve-2.3-diff-backup-addon
    

    For PVE 3.0 (deprecated):

    wget http://ayufan.eu/projects/proxmox-ve-differential-backups/pve-3.0-diff-backup-addon
    

    For PVE 3.1 (deprecated):

    wget http://ayufan.eu/projects/proxmox-ve-differential-backups/pve-3.1-diff-backup-addon
    

    For PVE 3.2 (deprecated):

    wget http://ayufan.eu/projects/proxmox-ve-differential-backups/pve-3.2-diff-backup-addon
    

    For PVE 3.3 (deprecated):

    wget http://ayufan.eu/projects/proxmox-ve-differential-backups/pve-3.3-diff-backup-addon
    

    For PVE 3.4 (deprecated):

    wget http://ayufan.eu/projects/proxmox-ve-differential-backups/pve-3.4-diff-backup-addon
    

    For PVE 4.0 (deprecated):

    wget http://ayufan.eu/projects/proxmox-ve-differential-backups/pve-4.0-diff-backup-addon
    

    For PVE 4.1 (deprecated):

    wget http://ayufan.eu/projects/proxmox-ve-differential-backups/pve-4.1-diff-backup-addon
    

    For PVE 4.1-22 (compatible with 4.1-22 and newer) (deprecated):

    wget http://ayufan.eu/projects/proxmox-ve-differential-backups/pve-4.1-22-diff-backup-addon
    

    For PVE 4.2 (deprecated):

    wget http://ayufan.eu/projects/proxmox-ve-differential-backups/pve-4.2-diff-backup-addon
    

    For PVE 3.4-14 (compatible with 3.4-14 and newer) (deprecated):

    wget http://ayufan.eu/projects/proxmox-ve-differential-backups/pve-3.4-14-diff-backup-addon
    

    For PVE 4.2-17 (compatible with 4.2-17 and newer) (deprecated):

    wget http://ayufan.eu/projects/proxmox-ve-differential-backups/pve-4.2-17-diff-backup-addon
    

    For PVE 4.3 (deprecated):

    wget http://ayufan.eu/projects/proxmox-ve-differential-backups/pve-4.3-diff-backup-addon
    

    For PVE 4.4 (deprecated):

    wget http://ayufan.eu/projects/proxmox-ve-differential-backups/pve-4.4-diff-backup-addon
    

    For PVE 4.4-13 (compatible with 4.4-13 and newer) (stable):

    wget http://ayufan.eu/projects/proxmox-ve-differential-backups/pve-4.4-13-diff-backup-addon
    

    For PVE 5.0 (stable):

    wget http://ayufan.eu/projects/proxmox-ve-differential-backups/pve-5.0-diff-backup-addon
    
  2. Execute bash script. The script contains all needed patches:
    bash pve-4.4-diff-backup-addon apply
    
  3. When everything went right, you’ll see:
    Proxmox VE 5.0 - differential backup support
    Kamil Trzcinski, http://ayufan.eu/, ayufan@ayufan.eu
    
    PATCHED: /usr/share/pve-manager/
    PATCHED: /usr/share/perl5/PVE/
    
    Restarting PVE API Proxy Server: pveproxy.
    Restarting PVE Daemon: pvedaemon.
    
  4. Download and install xdelta3. If you want to use LZOP compressor, you have to download my xdelta3 compilation.
    wget http://ayufan.eu/projects/proxmox-ve-differential-backups/pve-xdelta3_3.0.6-1_amd64.deb
    dpkg -i pve-xdelta3_3.0.6-1_amd64.deb
    

    However, if you paranoid about installing untrusted applications you can compile the package yourself. All the sources can be found here: pve-xdelta3-master.tar.bz2

    Previous release of xdelta was 3.0.5. Please update to the newer one: 3.0.6.

And what about uninstall?

The procedure is simpler than installation. Type in the bash:

    bash pve-5.0-diff-backup-addon revert

After a while, you’ll see:

    Proxmox VE 5.0 - differential backup support
    Kamil Trzcinski, http://ayufan.eu/, ayufan@ayufan.eu

    RESTORED: /usr/share/pve-manager/
    RESTORED: /usr/share/perl5/PVE/

    Restarting PVE API Proxy Server: pveproxy.
    Restarting PVE Daemon: pvedaemon.

What about UPGRADE? (READ THIS)

This is important part. If you will ever want to upgrade your Proxmox installation (by apt-get dist-upgrade or apt-get upgrade) ALWAYS revert/uninstall patches. You will still be able to apply them afterwards.

How to apply new patch version?

  • Use previous patch to revert changes.
  • Download new patch version and apply as described before.

The results

The results are really astonishing! These are real word values:

    VM   full      diff 1day   diff 2days   diff 3days    diff 4days
    1.   39.10GB   41MB        47MB         51MB          55MB
    2.   96.84GB   1.07GB      1.38GB       1.43GB        1.68GB
    3.   83.95GB   1.68GB      2.66GB       3.69GB        4.25GB
    4.   9.19GB    76KB        76KB         166MB         198MB

You see the differences. The diff sizes strictly depends on the use of the VMs. Using differential backups I have backups from last month (full backup once a week, differential daily)

Why this is not upstream?

I tried to push the changes upstream. They were rejected by Dietmar:

We removed that feature 3 years ago. I have no plans to re-add that. We want to keep vzdump a simple tool.

But I thought that it would be really shame if I wouldn’t go public with this.

Is it stable?

Yes, it is. This extensions uses xdelta3 as differential backup tool, which proven to be well tested and stable. I use it for about 9 months on 4 different Proxmox based servers. No problems so far.

However, if you happen to be paranoidal about backups… You should consider running following script. The script simply tries to verify all differential backups. I recently updated the script to support new VMA archive. So now you can verify backups all supported backups.

    wget http://ayufan.eu/projects/proxmox-ve-differential-backups/pve-verify-backups
    chmod +x pve-verify-backups
    ./pve-verify-backups <backup-dir>

FAQ

In case of any problems applying or reverting patches you can always simple revert back to stock. Simply reinstall modified packages:

    apt-get --reinstall install pve-manager qemu-server libpve-storage-perl

Then you can try to reapply patches once again.

In order to remove all leftovers you have to edit /etc/pve/vzdump.cron and remove fullbackup switch from vzdump command line.

Changelog

  • v1: initial public release with support for PVE2.2 and PVE2.3 (2013-03-05)
  • v2: improved kvm backup size and speed for PVE2.3 (2013-03-08)
  • v3: added support for PVE3.0 (2013-06-02)
  • v3′: updated pve-verify-backups to support VMA archives (2013-06-06)
  • v3”: updated patches to support PVE3.1 (2013-08-24)
  • v3”: updated xdelta3 to 3.0.6. More info about changes: http://xdelta.org/ (2013-08-24)
  • v3”: updated patches to support PVE3.2 (2014-03-15)
  • v3”: added FAQ (2014-04-30)
  • v3”: updated patches to support PVE3.3 (2014-09-23)
  • v3”: updated patches to support PVE3.4 (2015-02-26)
  • v3”: updated patches to support PVE4.0 (2015-11-07)
  • v3”: updated patches to support PVE4.1 (2016-01-22)
  • v3”: updated patches to support PVE4.1-22 (2016-04-13)
  • v3”: updated patches to support PVE4.2 (2016-05-02)
  • v3”: updated patches to support PVE3.4-14 (2016-08-02)
  • v3”: updated patches to support PVE4.2-17 (2016-08-02)
  • v3”: updated patches to support PVE4.3 (2016-10-24)
  • v3”: updated patches to support PVE4.4 (2017-01-23)
  • v3”: updated patches to support PVE4.4-13 (2017-04-10)
  • v3”: updated patches to support PVE5.0 (2017-07-20)

Detailed list of changes

  1. pve-xdelta3:
  2. vzdump:
    • added “fullbackup” option
  3. qmrestore and vzrestore:
    • added support for differential backups
  4. PVE.dc.BackupEdit:
    • added controls for maxfiles and fullbackup

Proxmox Free Community upgrade from 4.4 to 5.x version

01. /etc/apt/sources.list
deb http://ftp.debian.org/debian jessie main contrib

# PVE pve-no-subscription repository provided by proxmox.com,
# NOT recommended for production use
deb http://download.proxmox.com/debian jessie pve-no-subscription

# security updates
deb http://security.debian.org jessie/updates main contrib

02. mv /etc/apt/sources.list.d/pve-enterprise.list /home

03. apt-get update

04. apt-get dist-upgrade

05. reboot

06. Virtual Environment 4.4-18/ef2610e8

07. /etc/apt/sources.list
deb http://ftp.debian.org/debian stretch main contrib

# PVE pve-no-subscription repository provided by proxmox.com,
# NOT recommended for production use
deb http://download.proxmox.com/debian/pve stretch pve-no-subscription

# security updates
deb http://security.debian.org stretch/updates main contrib

08. apt-get update

09. apt-get dist-upgrade

10. reboot

11. Virtual Environment 5.0-32/2560e073

Soure: https://forum.proxmox.com/threads/test-upgrade-from-community-4-4-to-5-x.37232/

MooseFS open-source version

MooseFS (GPLv2) is an open-source version of MooseFS targeting open-source community. It is a natural continuation of previous MooseFS editions.

MooseFS is a key system for Gemius / Core Technology in-house operations. We currently store over 4.9 PB of data, processing more than 200 000 events per second, every second, 24/7. The system is so crucial, that we do not allow anyone outside of our own development team to make changes in the structure of the code used by us.

Therefore our philosophy is to give this superb tool to everyone who would like to use it. We have never aimed to create a developers community, although your ideas, bug reports and wishes are carefully taken into account by our developers. We look forward to your comments and patches, but it does not necessarily mean we will include those

https://moosefs.com/about/#advantages

https://www.youtube.com/watch?time_continue=112&v=eZs2Z9fCNqs

How to migrate a Windows PC to a Parallels Desktop virtual machine

Symptoms

You have a Windows PC, and you want to migrate it, along with all its content, to a Parallels Desktop for Mac virtual machine.

Resolution

You can import all your data from a Windows PC to Parallels Desktop on your Mac. Then you can continue to work with all your Windows programs, files, and data side-by-side with OS X.

Important: After importing your data from your PC, you may need to reactivate some of your Windows programs using the activation keys you received when you purchased the programs.


Note: After migration is complete your PC will remain unmodified. See related article KB 117639


Requirements for importing your data

To import data to your Mac, you need a Windows computer with the following specifications:

For Parallels Transported Agent v.9:

  • Windows XP with Service Pack 2 or later, Windows Vista, Windows 7 or Windows 8.

    Note: You can also use a computer running Windows Server 2008 R2 (64-bit only), Windows Server 2008, or Windows 2000 Professional (32-bit only).

  • An Intel or AMD (700 MHz or higher) x86 or x64 processor
  • At least 256 MB of RAM
  • At least 70 MB of hard disk space for installing Parallels Transporter Agent
  • One of the following:
    • An Ethernet port for transferring your data over the network
    • A USB port for transferring your data using the Parallels USB cable
  • An external storage device, such as a USB hard disk
  • Supported Windows and Linux versions:**
    • Windows 8.1
    • Windows 7
    • Windows Vista
    • Windows XP
    • Windows Server 2003
    • Windows 2000
    • Red Hat Enterprise Linux 5.x, 6.x
    • Ubuntu Linux 10.04 LTS, 14.04

For Parallels Transporter Agent v.10

See the Parallels Transporter Agent User’s Guide)

  • 700 MHz (or higher) x86 or x64 processor (Intel or AMD)
  • 256 MB or more of RAM
  • 50 MB of hard disk space for installing Parallels Transporter Agent
  • Ethernet or WiFi network adapter for migrating over network
  • Supported Windows and Linux versions:
    • Windows 8.1
    • Windows 7
    • Windows Vista
    • Windows XP
    • Windows Server 2003
    • Windows 2000
    • Red Hat Enterprise Linux 5.x, 6.x
    • Ubuntu Linux 10.04 LTS, 14.04

Note: Parallels Desktop does not support migrating Windows dynamic volumes (in which size is not fixed, as it is in basic volumes). They are migrated as data disks only. You can add them later to an existing virtual machine.

Also read KB #119172 before proceeding with migration.

Step 1: Install Parallels Transporter Agent on your Windows PC

To import your data, you must first install the Parallels Transporter Agent software on the Windows PC.

Do one of the following:

  • If you purchased a physical copy of Parallels Desktop, insert the installation DVD into your Windows PC. If the installation doesn’t start automatically, locate and double-click the Parallels Transporter Agent.exe file.
  • Download Parallels Transporter Agent for Windows from the Parallels website and double-click the installation file.

If your computer is connected to the Internet, Parallels Transporter Agent checks for available updates. If an update is available, click Download and Install New Version. Follow the onscreen instructions to install Parallels Transporter Agent.

Step 2: Import Your Data

Choose one of the methods below for importing your data from your PC to your Mac.

Using a Parallels USB cable

The Parallels USB cable required for this method is included with Parallels Desktop Switch to Mac Edition. If you don’t have the Parallels USB cable, import your data using one of the other methods.


Note: Parallels USB Cable is available only for Parallels Desktop 8 Switch to Mac Edition and earlier.


  1. Turn on your Mac and your Windows PC then log in to both computers.
  2. On the Windows PC, open Parallels Transporter Agent by clicking the Start menu and selecting All Programs > Parallels > Parallels Transporter Agent.
  3. Connect the Parallels USB cable to your Windows PC and your Mac.
  4. If the Windows PC is running Windows XP, the Found New Hardware wizard opens. In this wizard:
    • Select Yes, this time only, and click Next.
    • Select Install the software automatically (Recommended), and click Next.
    • A Hardware Installation warning appears. Click Continue Anyway.
    • Drivers for the Parallels USB cable are installed. Click Finish to exit the wizard.
  5. On your Mac, open Parallels Desktop and choose File > New.
  6. Select Migrate from a PC and click Continue.
  7. Select Parallels USB cable and click Continue. Parallels Transporter will start collecting information about the source computer.
  8. If the Windows Installation Files window appears, insert the Windows installation disc into your Mac and click Continue.
  9. If you don’t want to log in to Windows automatically whenever you start up, select “Do not enable Automatic Logon”. Then click Continue.
  10. Choose whether you want to migrate all your files and data or only Windows applications. Then click Continue.
  11. Choose where you want to install your data. You can also click Customize and select which Windows volumes to migrate. Then click Continue.
  12. In the next step you will see a warning about Windows activation that might be required when you start using it. To proceed, read this message, select I want to continue and click Continue.
  13. Once the migration is complete, click Done.
  14. Start Windows.
  15. Once Windows starts up, choose Virtual Machine > Install Parallels Tools and follow the onscreen instructions.

Note: To be able to install Parallels Tools, you must be logged in to Windows as an administrator.

Over a network

Important: After importing your data, you may need to reactivate some of your Windows programs using the activation keys you received when you purchased the programs. To import your data from a PC over a network:

  1. Turn on your Mac and your Windows PC then log in to both. Verify sure that the computers are connected over the same network.
  2. Make sure that the Windows firewall is turned off. You can turn it on again after the import is finished.
  3. On the Windows PC, open Parallels Transporter Agent. From the Start menu select All Programs > Parallels > Parallels Transporter Agent.
  4. On your Mac, open Parallels Desktop and choose File > New.
  5. Select “Migrate from a PC” and click Continue.
  6. Select “Network” and click Continue.
  7. Find the passcode displayed in Parallels Wizard on your Mac and enter it in Parallels Transporter Agent on your Windows PC. You can also connect to the source Windows PC using its name or IP address: click “Use IP address instead”, select the Windows PC name from the list or type the IP address, and click Continue.
  8. If you have chosen to use the computer name or IP address, provide the Windows administrator credentials. Parallels Desktop will connect to Parallels Transporter Agent and start collecting information about the source computer.
  9. If the Windows Installation Files window appears, insert the Windows installation disc into your Mac and click Continue.
  10. If you don’t want to log in to Windows automatically whenever you start up, select “Do not enable Automatic Logon”. Then click Continue.
  11. Choose whether you want to migrate all your files and data or only Windows applications. Then click Continue.
  12. Choose where you want to install your data. You can also click Customize and select which Windows volumes to migrate. Then click Continue.
  13. In the next step you will see a warning about Windows activation that might be required when you start using it. To proceed, read this message, select “I want to continue” and click Continue.
  14. Once the migration is complete, click Done.
  15. Start Windows.
  16. When Windows boots up, choose Virtual Machine > Install Parallels Tools and follow the onscreen instructions.

Note: To be able to install Parallels Tools, you must be logged in to Windows as an administrator.

Using an External Storage Device

Important: After importing your data, you may need to reactivate some of your Windows programs using the activation keys you received when you purchased the programs. To import your data from a PC using an external storage device:

  1. Connect an external storage device to your Windows PC.
  2. In the Windows PC, open Parallels Transporter Agent by clicking the Start menu and selecting All Programs > Parallels > Parallels Transporter Agent.
  3. Click the external storage device icon.
  4. Click Next. Parallels Transporter Agent will collect information about the Windows PC.
  5. If you don’t want to log in to Windows automatically whenever you start up, select “Do not enable Automatic Logon”. Then click Next.
  6. Choose whether you want to migrate all your files and data or only Windows applications. Then click Next.
  7. Choose where you want to store your data. You can also click Customize and select which Windows volumes to migrate. Then click Next.
  8. In the next step you will see a warning about Windows activation that might be required when you start using it. To proceed, read this message, select “I want to continue” and click Next.
  9. Once the migration is complete, click Done to quit Parallels Transporter Agent.
  10. Disconnect the storage device from the Windows PC and connect it to your Mac.
  11. On your Mac, open Parallels Desktop and choose File > New.
  12. Select “Migrate from a PC” and click Continue.
  13. Select “External Storage Device” and click Continue.
  14. Click “Choose” and locate where you chose to store your data in step 7. Then click Continue.
  15. Choose where you want to install Windows and your data, then click Continue.
  16. Once the migration is complete, click Done.
  17. Start Windows.
  18. When Windows boots up, choose Virtual Machine > Install Parallels Tools and follow the onscreen instructions.

Note: To be able to install Parallels Tools, you must be logged in to Windows as an administrator.

For more information about migrating your PC to Mac please also visit our on-line User’s Guide

If you have an issue with migration, please follow the solution outlined in KB #113269.


Related articles:

Source: http://kb.parallels.com/eu/115007

Netdata Custom Dashboards

You can:

  • create your own dashboards using simple HTML (no javascript is required for basic dashboards)
  • utilizing any or all of the available chart libraries, on the same dashboard
  • using data from one or more netdata servers, on the same dashboard
  • host your dashboard HTML page on any web server, anywhere

netdata charts can also be added to existing web pages.

Check this very simple working example of a custom dashboard, and its html source.

If you plan to put it on TV, check tv.html. This is a screenshot of it, monitoring 2 servers on the same page:

image

Web directory

The default web root directory is /usr/share/netdata/web where you will find examples such as tv.html, and demo.html as well as the main dashboard contained in index.html.
Note: index.html have a different syntax. Don’t use it as a template for simple custom dashboards.

Example empty dashboard

If you need to create a new dashboard on an empty page, we suggest the following header:

<!DOCTYPE html>
<html lang="en">
<head>
	<title>Your dashboard</title>

	<meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
	<meta charset="utf-8">
	<meta http-equiv="X-UA-Compatible" content="IE=edge,chrome=1">
	<meta name="viewport" content="width=device-width, initial-scale=1">
	<meta name="apple-mobile-web-app-capable" content="yes">
	<meta name="apple-mobile-web-app-status-bar-style" content="black-translucent">

	<!-- here we will add dashboard.js -->

</head>
<body>

<!-- here we will add charts -->

</body>
</html>

dashboard.js

To add netdata charts to any web page (dedicated to netdata or not), you need to include the /dashboard.js file of a netdata server.

For example, if your netdata server listens at http://box:19999/, you will need to add the following to the head section of your web page:

<script type="text/javascript" src="http://box:19999/dashboard.js"></script>

what dashboard.js does?

dashboard.js will automatically load the following:

  1. dashboard.css, required for the netdata charts
  2. jquery.min.js, (only if jquery is not already loaded for this web page)
  3. bootstrap.min.js (only if bootstrap is not already loaded) and bootstrap.min.css.You can disable this by adding the following before loading dashboard.js:
<script>var netdataNoBootstrap = true;</script>
  1. jquery.nanoscroller.min.js, required for the scrollbar of the chart legends.
  2. bootstrap-toggle.min.js and bootstrap-toggle.min.css, required for the settings toggle buttons.
  3. font-awesome.min.css, for icons.

When dashboard.js loads will scan the page for elements that define charts (see below) and immediately start refreshing them. Keep in mind more javascript modules may be loaded (every chart library is a different javascript file, that is loaded on first use).

Prevent dashboard.js from starting chart refreshes

If your web page is not static and you plan to add charts using javascript, you can tell dashboard.js not to start processing charts immediately after loaded, by adding this fragment before loading it:

<script>var netdataDontStart = true;</script>

The above, will inform the dashboard.js to load everything, but not process the web page until you tell it to. You can tell it to start processing the page, by running this javascript code:

NETDATA.start();

Be careful not to call the NETDATA.start() multiple times. Each call to this function will spawn a new thread that will start refreshing the charts.

If, after calling NETDATA.start() you need to update the page (or even get your javascript code synchronized with dashboard.js), you can call (after you loaded dashboard.js):

NETDATA.pause(function() {
  // ok, it is paused

  // update the DOM as you wish

  // and then call this to let the charts refresh:
  NETDATA.unpause();
});

The default netdata server

dashboard.js will attempt to auto-detect the URL of the netdata server it is loaded from, and set this server as the default netdata server for all charts.

If you need to set any other URL as the default netdata server for all charts that do not specify a netdata server, add this before loading dashboard.js:

<script type="text/javascript">var netdataServer = "http://your.netdata.server:19999";</script>

Adding charts

To add charts, you need to add a div for each of them. Each of these div elements accept a few data- attributes:

The chart unique ID

The unique ID of a chart is shown at the title of the chart of the default netdata dashboard. You can also find all the charts available at your netdata server with this URL: http://your.netdata.server:19999/api/v1/charts (example).

To specify the unique id, use this:

<div data-netdata="unique.id"></div>

The above is enough for adding a chart. It most probably have the wrong visual settings though. Keep reading…

The duration of the chart

You can specify the duration of the chart (how much time of data it will show) using:

<div data-netdata="unique.id"
     data-after="AFTER_SECONDS"
     data-before="BEFORE_SECONDS"
     ></div>

AFTER_SECONDS and BEFORE_SECONDS are numbers representing a time-frame in seconds.

The can be either:

  • absolute unix timestamps (in javascript terms, they are new Date().getTime() / 1000. Using absolute timestamps you can have a chart showing always the same time-frame.
  • relative number of seconds to now. To show the last 10 minutes of data, AFTER_SECONDS must be -600 (relative to now) and BEFORE_SECONDS must be 0 (meaning: now). If you want the chart to auto-refresh the current values, you need to specify relative values.

Chart dimensions

You can set the dimensions of the chart using this:

<div data-netdata="unique.id"
     data-width="WIDTH"
     data-height="HEIGHT"
     ></div>

WIDTH and HEIGHT can be anything CSS accepts for width and height (e.g. percentages, pixels, etc). Keep in mind that for certain chart libraries, dashboard.js may apply an aspect ratio to these.

If you want dashboard.js to remember permanently (browser local storage) the dimensions of the chart (the user may resize it), you can add: data-id="SETTINGS_ID", where SETTINGS_ID is anything that will be common for this chart across user sessions.

Netdata server

Each chart can get data from a different netdata server. You can give per chart the netdata server using:

<div data-netdata="unique.id"
     data-host="http://another.netdata.server:19999/"
     ></div>

Chart library

The default chart library is dygraph. You set a different chart library per chart using this:

<div data-netdata="unique.id"
     data-chart-library="gauge"
     ></div>

Each chart library may support more chart-library specific settings. Please refer to the documentation of the chart library you are interested, in this wiki.

Data points

For the time-frame requested, dashboard.js will use the chart dimensions and the settings of the chart library to find out how many data points it can show.

For example, most line chart libraries are using 3 pixels per data point. If the chart shows 10 minutes of data (600 seconds), its update frequency is 1 second, and the chart width is 1800 pixels, then dashboard.js will request from the netdata server: 10 minutes of data, represented in 600 points, and the chart will be refreshed per second. If the user resizes the window so that the chart becomes 600 pixels wide, then dashboard.js will request the same 10 minutes of data, represented in 200 points and the chart will be refreshed once every 3 seconds.

If you need to have a fixed number of points in the data source retrieved from the netdata server, you can set:

<div data-netdata="unique.id"
     data-points="DATA_POINTS"
     ></div>

Where DATA_POINTS is the number of points you need.

You can also overwrite the pixels-per-point per chart using this:

<div data-netdata="unique.id"
     data-pixels-per-point="PIXELS_PER_POINT"
     ></div>

Where PIXELS_PER_POINT is the number of pixels each data point should occupy.

Data grouping method

Netdata supports average (the default) or max grouping methods. The grouping method is used when the netdata server is requested to return fewer points for a time-frame, compared to the number of points available.

You can give it per chart, using:

<div data-netdata="unique.id"
     data-method="max"
     ></div>

Selecting dimensions

By default, dashboard.js will show all the dimensions of the chart. You can select specific dimensions using this:

<div data-netdata="unique.id"
     data-dimensions="dimension1,dimension2,dimension3,..."
     ></div>

Chart title

You can overwrite the title of the chart using this:

<div data-netdata="unique.id"
     data-title="my super chart"
     ></div>

Chart units

You can overwrite the units of measurement of the dimensions of the chart, using this:

<div data-netdata="unique.id"
     data-units="words/second"
     ></div>

Chart colors

dashboard.js has an internal palette of colors for the dimensions of the charts. You can prepend colors to it (so that your will be used first) using this:

<div data-netdata="unique.id"
     data-colors="#AABBCC #DDEEFF ..."
     ></div>

Extracting dimension values

dashboard.js can update the selected values of the chart at elements you specify. For example, let’s assume we have a chart that measures the bandwidth of eth0, with 2 dimensions in and out. You can use this:

<div data-netdata="net.eth0"
     data-show-value-of-in-at="eth0_in_value"
     data-show-value-of-out-at="eth0_out_value"
     ></div>

My eth0 interface, is receiving <span id="eth0_in_value"></span>
and transmitting <span id="eth0_out_value"></span>.

Hiding the legend of a chart

On charts that by default have a legend managed by dashboard.js you can remove it, using this:

<div data-netdata="unique.id"
     data-legend="no"
     ></div>

API options

You can append netdata REST API v1 data options, using this:

<div data-netdata="unique.id"
     data-append-options="absolute,percentage"
     ></div>

Chart library performance

dashboard.js measures the performance of the chart library when it renders the charts. You can specify an element ID you want this information to be visualized, using this:

<div data-netdata="unique.id"
     data-dt-element-name="measurement1"
     ></div>

refreshed in <span id="measurement1"></span> milliseconds!

https://github.com/firehol/netdata/wiki/Custom-Dashboards

Back to top