FTP (port 21) and SFTP (port 22) are supported, using your login and password in the Cloud Storage panel.

# You must have mutt installed for email alerts and curl installed to upload the files to the ftp server.
# Change settings to match your settings!
# !/bin/bash

# Date for files
DATE=`date +%A_%b_%d_%Y`

# Home Directory
HOMEDIR=/backup

# FTP Username
USERNAME=username

# FTP Password
FTPPASSWORD=password

# FTP Hostname or IP Address
HOSTNAME=127.0.0.1

# Server Name
SERVERNAME=server1

# Send Confirmation email to this address
EMAILADDRESS1=user@domainname.com

# Uptime
UPTIME=`uptime`

#Make Directory
mkdir /backup/$DATE >> /backup/$DATE.log

# MySQL
DBUSER=database user
DBPSWD=database password
DATABASE1=database

# Touch Log file
echo "-+-+-+-+-" >> $HOMEDIR/$DATE.log
echo $DATE >> $HOMEDIR/$DATE.log
echo "-+-+-+-+-" >> $HOMEDIR/$DATE.log
echo $UPTIME >> $HOMEDIR/$DATE.log

# Backup Databases
mysqldump -u $DBUSER -p$DBPSWD $DATABASE1 > $HOMEDIR/$DATE/$DATABASE1.sql >> $HOMEDIR/$DATE.log

# rsync Meta partition to $BACKDIR/$DATE/
rsync -a -v /var/www/ /backup/$DATE/www/ >> /backup/$DATE.log

# TAR UP FILES
tar -czf $HOMEDIR/$SERVERNAME$DATE.tar.gz /backup/$DATE >> /backup/$DATE.log

# Send backup files to redundant back up server
curl -T $HOMEDIR/$SERVERNAME$DATE.tar.gz ftp://$USERNAME:$FTPPASSWORD@$HOSTNAME:21/$SERVERNAME$DATE.tar.gz >> $HOMEDIR/$DATE.log


#Mail user when complete
mutt -s "Back up complete $UPTIME" -c $EMAILADDRESS1 -i $HOMEDIR/$DATE.log >> $HOMEDIR/$DATE.log

The post Cloud Storage: FTP / SFTP How to appeared first on Hivelocity Hosting.

Installing fuse-sshfs

Debian/Ubuntu

apt-get install sshfs

CentOS

wget https://dl.fedoraproject.org/pub/epel/6/x86_64/epel-release-6-8.noarch.rpm

rpm -Uvh epel-release-6-8.noarch.rpm

yum install fuse-sshfs

Setup sshmount

Create the mountpoint directory:

mkdir /mnt/sshfs_mount

Connect and mount with sshfs:

sshfs user@hostname:/ /mnt/sshfs_mount/

If the Cloud Storage panel informs you to connect to cloudstorage3.hivelocity.net or cloudstorage4.hivelocity.net, use the full path to your remote home directory:

sshfs user@hostname:/home/user/ /mnt/sshfs_mount/

You may now write to your newly mounted storage in /mnt/sshfs_mount/.

Using rsync

Synchronizing a local directory with a remote one:

rsync -r -a -v --delete /home /mnt/sshfs_mount

CentOS Example:

[root@centos6 ~]# wget https://dl.fedoraproject.org/pub/epel/6/x86_64/epel-release-6-8.noarch.rpm
    --2014-01-22 07:10:58--  https://dl.fedoraproject.org/pub/epel/6/x86_64/epel-release-6-8.noarch.rpm
    Resolving dl.fedoraproject.org... 209.132.181.25, 209.132.181.26, 209.132.181.27, ...
    Connecting to dl.fedoraproject.org|209.132.181.25|:80... connected.
    HTTP request sent, awaiting response... 200 OK
    Length: 14540 (14K) [application/x-rpm]
    Saving to: âepel-release-6-8.noarch.rpmâ
    100%[======================================>] 14,540      --.-K/s   in 0.04s
    2014-01-22 07:10:58 (331 KB/s) - âepel-release-6-8.noarch.rpmâ

    [root@centos6 ~]# rpm -Uvh epel-release-6-8.noarch.rpm
    warning: epel-release-6-8.noarch.rpm: Header V3 RSA/SHA256 Signature, key ID 060                                            8b895: NOKEY
    Preparing...                ########################################### [100%]
       1:epel-release           ########################################### [100%]

    [root@centos6 ~]# yum install fuse-sshfs
    Loaded plugins: fastestmirror
    Loading mirror speeds from cached hostfile
    epel/metalink                                            |  14 kB     00:00
     * base: ftp.usf.edu
     * epel: mirror.cogentco.com
     * extras: mirror.oss.ou.edu
     * updates: mirror.oss.ou.edu
    epel                                                     | 4.2 kB     00:00
    epel/primary_db                                          | 5.8 MB     00:00
    Setting up Install Process
    Resolving Dependencies
    --> Running transaction check
    ---> Package fuse-sshfs.x86_64 0:2.4-1.el6 will be installed
    --> Processing Dependency: fuse >= 2.2 for package: fuse-sshfs-2.4-1.el6.x86_64
    --> Processing Dependency: openssh-clients for package: fuse-sshfs-2.4-1.el6.x86_64
    --> Processing Dependency: libfuse.so.2(FUSE_2.7)(64bit) for package: fuse-sshfs-2.4-1.el6.x86_64
    --> Processing Dependency: libfuse.so.2(FUSE_2.6)(64bit) for package: fuse-sshfs-2.4-1.el6.x86_64
    --> Processing Dependency: libfuse.so.2(FUSE_2.5)(64bit) for package: fuse-sshfs-2.4-1.el6.x86_64
    --> Processing Dependency: libfuse.so.2(FUSE_2.4)(64bit) for package: fuse-sshfs-2.4-1.el6.x86_64
    --> Processing Dependency: libfuse.so.2(FUSE_2.2)(64bit) for package: fuse-sshfs-2.4-1.el6.x86_64
    --> Processing Dependency: libfuse.so.2()(64bit) for package: fuse-sshfs-2.4-1.el6.x86_64
    --> Running transaction check
    ---> Package fuse.x86_64 0:2.8.3-4.el6 will be installed
    ---> Package fuse-libs.x86_64 0:2.8.3-4.el6 will be installed
    ---> Package openssh-clients.x86_64 0:5.3p1-94.el6 will be installed
    --> Processing Dependency: openssh = 5.3p1-94.el6 for package: openssh-clients-5.3p1-94.el6.x86_64
    --> Processing Dependency: libcrypto.so.10(libcrypto.so.10)(64bit) for package: openssh-clients-5.3p1-94.el6.x86_64
    --> Processing Dependency: libcrypto.so.10(OPENSSL_1.0.1)(64bit) for package: openssh-clients-5.3p1-94.el6.x86_64
    --> Processing Dependency: libedit.so.0()(64bit) for package: openssh-clients-5.3p1-94.el6.x86_64
    --> Running transaction check
    ---> Package libedit.x86_64 0:2.11-4.20080712cvs.1.el6 will be installed
    ---> Package openssh.x86_64 0:5.3p1-84.1.el6 will be updated
    --> Processing Dependency: openssh = 5.3p1-84.1.el6 for package: openssh-server-5.3p1-84.1.el6.x86_64
    ---> Package openssh.x86_64 0:5.3p1-94.el6 will be an update
    ---> Package openssl.x86_64 0:1.0.0-27.el6 will be updated
    ---> Package openssl.x86_64 0:1.0.1e-16.el6_5.4 will be an update
    --> Processing Dependency: make for package: openssl-1.0.1e-16.el6_5.4.x86_64
    --> Running transaction check
    ---> Package make.x86_64 1:3.81-20.el6 will be installed
    ---> Package openssh-server.x86_64 0:5.3p1-84.1.el6 will be updated
    ---> Package openssh-server.x86_64 0:5.3p1-94.el6 will be an update
    --> Finished Dependency Resolution
    Dependencies Resolved
    ================================================================================
     Package             Arch       Version                       Repository   Size
    ================================================================================
    Installing:
     fuse-sshfs          x86_64     2.4-1.el6                     epel         52 k
    Installing for dependencies:
     fuse                x86_64     2.8.3-4.el6                   base         71 k
     fuse-libs           x86_64     2.8.3-4.el6                   base         74 k
     libedit             x86_64     2.11-4.20080712cvs.1.el6      base         74 k
     make                x86_64     1:3.81-20.el6                 base        389 k
     openssh-clients     x86_64     5.3p1-94.el6                  base        402 k
    Updating for dependencies:
     openssh             x86_64     5.3p1-94.el6                  base        258 k
     openssh-server      x86_64     5.3p1-94.el6                  base        311 k
     openssl             x86_64     1.0.1e-16.el6_5.4             updates     1.5 M

    Transaction Summary
    ================================================================================
    Install       6 Package(s)
    Upgrade       3 Package(s)

    Total download size: 3.1 M
    Is this ok [y/N]: y
    Downloading Packages:
    (1/9): fuse-2.8.3-4.el6.x86_64.rpm                       |  71 kB     00:00
    (2/9): fuse-libs-2.8.3-4.el6.x86_64.rpm                  |  74 kB     00:00
    (3/9): fuse-sshfs-2.4-1.el6.x86_64.rpm                   |  52 kB     00:00
    (4/9): libedit-2.11-4.20080712cvs.1.el6.x86_64.rpm       |  74 kB     00:00
    (5/9): make-3.81-20.el6.x86_64.rpm                       | 389 kB     00:00
    (6/9): openssh-5.3p1-94.el6.x86_64.rpm                   | 258 kB     00:00
    (7/9): openssh-clients-5.3p1-94.el6.x86_64.rpm           | 402 kB     00:00
    (8/9): openssh-server-5.3p1-94.el6.x86_64.rpm            | 311 kB     00:00
    (9/9): openssl-1.0.1e-16.el6_5.4.x86_64.rpm              | 1.5 MB     00:00
    --------------------------------------------------------------------------------
    Total                                           2.5 MB/s | 3.1 MB     00:01
    warning: rpmts_HdrFromFdno: Header V3 RSA/SHA256 Signature, key ID 0608b895: NOKEY
    Retrieving key from file:///etc/pki/rpm-gpg/RPM-GPG-KEY-EPEL-6
    Importing GPG key 0x0608B895:
     Userid : EPEL (6) <epel@fedoraproject.org> 
 Package: epel-release-6-8.noarch (installed) 
 From : /etc/pki/rpm-gpg/RPM-GPG-KEY-EPEL-6
 Is this ok [y/N]: y 
 Running rpm_check_debug 
 Running Transaction Test
 Transaction Test Succeeded 
 Running Transaction
 Warning: RPMDB altered outside of yum.
 Installing : 1:make-3.81-20.el6.x86_64 1/12 
 Updating : openssl-1.0.1e-16.el6_5.4.x86_64 2/12 
 Updating : openssh-5.3p1-94.el6.x86_64 3/12 
 Installing : fuse-libs-2.8.3-4.el6.x86_64 4/12 
 Installing : fuse-2.8.3-4.el6.x86_64 5/12 
 Installing : libedit-2.11-4.20080712cvs.1.el6.x86_64 6/12 
 Installing : openssh-clients-5.3p1-94.el6.x86_64 7/12 
 Installing : fuse-sshfs-2.4-1.el6.x86_64 8/12 
 Updating : openssh-server-5.3p1-94.el6.x86_64 9/12 
 Cleanup : openssh-server-5.3p1-84.1.el6.x86_64 10/12 
 Cleanup : openssh-5.3p1-84.1.el6.x86_64 11/12 
 Cleanup : openssl-1.0.0-27.el6.x86_64 12/12 
 Verifying : libedit-2.11-4.20080712cvs.1.el6.x86_64 1/12 
 Verifying : openssl-1.0.1e-16.el6_5.4.x86_64 2/12 
 Verifying : fuse-2.8.3-4.el6.x86_64 3/12 
 Verifying : openssh-5.3p1-94.el6.x86_64 4/12 
 Verifying : openssh-server-5.3p1-94.el6.x86_64 5/12 
 Verifying : fuse-sshfs-2.4-1.el6.x86_64 6/12 
 Verifying : openssh-clients-5.3p1-94.el6.x86_64 7/12 
 Verifying : fuse-libs-2.8.3-4.el6.x86_64 8/12 
 Verifying : 1:make-3.81-20.el6.x86_64 9/12 
 Verifying : openssh-server-5.3p1-84.1.el6.x86_64 10/12 
 Verifying : openssh-5.3p1-84.1.el6.x86_64 11/12 
 Verifying : openssl-1.0.0-27.el6.x86_64 12/12 
 Installed: 
 fuse-sshfs.x86_64 0:2.4-1.el6 
 Dependency Installed: 
 fuse.x86_64 0:2.8.3-4.el6      fuse-libs.x86_64 0:2.8.3-4.el6             libedit.x86_64 0:2.11-4.20080712cvs.1.el6 
 make.x86_64 1:3.81-20.el6 openssh-clients.x86_64 0:5.3p1-94.el6 
 Dependency Updated: 
 openssh.x86_64 0:5.3p1-94.el6 openssh-server.x86_64 0:5.3p1-94.el6 openssl.x86_64 0:1.0.1e-16.el6_5.4 
 Complete!

 [root@centos6 ~]# mkdir /cloudstorage 
 [root@centos6 ~]# sshfs caccount_1077@cloudstorage2.hivelocity.net:/ /cloudstorage/ 
 The authenticity of host 'cloudstorage2.hivelocity.net (206.51.235.186)' can't be established.
 RSA key fingerprint is 52:ba:48:2b:31:d9:c1:ea:ea:ea:c0:a2:22:db:a5:98. 
 Are you sure you want to continue connecting (yes/no)? yes 
 caccount_1077@cloudstorage2.hivelocity.net's password: 

 [root@centos6 ~]# mount
 /dev/mapper/vg_centos6-lv_root on / type ext4 (rw) 
 proc on /proc type proc (rw) 
 sysfs on /sys type sysfs (rw) 
 devpts on /dev/pts type devpts (rw,gid=5,mode=620) .
 tmpfs on /dev/shm type tmpfs (rw,rootcontext="system_u:object_r:tmpfs_t:s0") 
 /dev/vda1 on /boot type ext4 (rw)
 /dev/mapper/vg_centos6-lv_home on /home type ext4 (rw)
 none on /proc/sys/fs/binfmt_misc type binfmt_misc (rw) 
 caccount_1077@cloudstorage2.hivelocity.net:/ on /cloudstorage type fuse.sshfs (rw,nosuid,nodev) 
 
 [root@centos6 ~]# cd /cloudstorage/ 
 
 [root@centos6 cloudstorage]# mkdir test 
 [root@centos6 cloudstorage]# ls -la 
 total 316 drwx------. 1 502 502 189 Jan 22 2014 . 
 dr-xr-xr-x. 23 root root 4096 Jan 22 07:14 .. 
 -rw-r--r--. 1 root root 107513 Sep 11 15:47 apf-current.tar.gz 
 -rwxr-xr-x. 1 root root 11264 Sep 11 15:45 aquota.group 
 -rw-r--r--. 1 502 502 18 Jul 18 2013 .bash_logout 
 -rw-r--r--. 1 502 502 176 Jul 18 2013 .bash_profile 
 -rw-r--r--. 1 502 502 124 Jul 18 2013 .bashrc 
 -rw-r--r--. 1 root root 12232 Sep 11 15:47 epel-release-5-4.noarch.rpm 
 -rw-r--r--. 1 root root 160381 Sep 11 15:47 iftop-0.17.tar.gz 
 drwxr-xr-x. 1 502 502 12 Jan 22 2014 test</epel@fedoraproject.org>

Ubuntu 12.0.4.3 Example:

root@logger:~# apt-get install sshfs
    Reading package lists... Done
    Building dependency tree
    Reading state information... Done
    The following NEW packages will be installed:
      sshfs
    0 upgraded, 1 newly installed, 0 to remove and 22 not upgraded.
    Need to get 43.9 kB of archives.
    After this operation, 129 kB of additional disk space will be used.
    Get:1 https://us.archive.ubuntu.com/ubuntu/ precise-updates/main sshfs amd64 2.3-1ubuntu0.1 [43.9 kB]
    Fetched 43.9 kB in 0s (207 kB/s)
    Selecting previously unselected package sshfs.
    (Reading database ... 139788 files and directories currently installed.)
    Unpacking sshfs (from .../sshfs_2.3-1ubuntu0.1_amd64.deb) ...
    Processing triggers for man-db ...
    Setting up sshfs (2.3-1ubuntu0.1) ...

    root@logger:~# mkdir /cloudstorage

    root@logger:~# sshfs caccount_1077@cloudstorage2.hivelocity.net:/ /cloudstorage/
    The authenticity of host 'cloudstorage2.hivelocity.net (206.51.235.186)' can't be established.
    RSA key fingerprint is 52:ba:48:2b:31:d9:c1:ea:f9:ac:c0:a2:22:db:a5:98.
    Are you sure you want to continue connecting (yes/no)? yes
    caccount_1077@cloudstorage2.hivelocity.net's password:

    root@logger:~# mount
    /dev/mapper/logger-root on / type ext4 (rw,errors=remount-ro)
    proc on /proc type proc (rw,noexec,nosuid,nodev)
    sysfs on /sys type sysfs (rw,noexec,nosuid,nodev)
    none on /sys/fs/fuse/connections type fusectl (rw)
    none on /sys/kernel/debug type debugfs (rw)
    none on /sys/kernel/security type securityfs (rw)
    udev on /dev type devtmpfs (rw,mode=0755)
    devpts on /dev/pts type devpts (rw,noexec,nosuid,gid=5,mode=0620)
    tmpfs on /run type tmpfs (rw,noexec,nosuid,size=10%,mode=0755)
    none on /run/lock type tmpfs (rw,noexec,nosuid,nodev,size=5242880)
    none on /run/shm type tmpfs (rw,nosuid,nodev)
    /dev/vda1 on /boot type ext2 (rw)
    caccount_1077@cloudstorage2.hivelocity.net:/ on /cloudstorage type fuse.sshfs (rw,nosuid,nodev,max_read=65536)

The post Cloud Storage: SSH Mount How to appeared first on Hivelocity Hosting.

Proxmox VE was developed by Proxmox Server Solutions in Austria under the Internet Foundation of Austria and is released under the GNU General Public License. Since it’s an opensource solution it can be customized as per your requirements.

Proxmox VE key points

a) Debian 6 64 bit based solution

b) Support latest Intel & AMD chipset

c) Combination of KVM & Openvz virtualization technology

d) Easy management Web Interface

e) Total control to create and manage virtual infrastructure

f) Broad Hardware Support

g) Optimize bare-metal virtualization to support high workloads

h) Scalable to 32 nodes

Proxmox VE Features

1) Management
Proxmox VE offers a simple web based management interface which is accessible after intstallation on the server. There is no need to install any additional tools or additional management nodes or external database. The management is done through the web interface based on a javascript framework and allows the administrator to control all the features.

Features of Management Interface

a) VNC console, SSL support

b) Based on Javascript Framework

c) Multiple Authentication methods

d) Dynamic updates of Resources

e) Create Virtual Servers & Containers

f) Handles thousands of VMs with Search capability

g) Role based user and permission management.

2) Flexible Storage

Promox offers a flexible storage model. The virtual machine images can either be stored on one or several local storage on shared storages like NFS and SAN.

Storing the Virtual Machines on shared storage allows for live migrations of running VMs with no down time.

Proxmox VE supported storage model

a) ZFS

b) NFS Share

c) Ceph RBD

d) ISCI target

e) GlusterFS

f) LVM Group

g) Director ( storage on existing file system )

3) Networking

Proxmox VE uses a bridged networking model. All VMs can share the same bridge as if virtual cables from each guest were plugged into the same switch. The bridge is then connected to the physical network adapters for the host server to which are assigned the ( TCP / IP ) network configuration so that the VMs can communicate to the outside world.

Proxmox VE supports VLANS , bonding and network aggregations which allows you to build complex flexible virtual networks for the hosts leveraging the full power of the Linux network stack.

4) Backup & Restore

Proxmox VE carries an integrated backup tool called as “vzdump” which creates snapshots of virtual guests both for Openvz & KVM. The vzdump tool creates a tarball of the VM or CT data that includes the virtual disks and all the configuration data.

Key points

a) Live backup

b) Backups can be scheduled

c) Graphical User Interface for Backup operations

d) Graphical User Interface for Restore operations

e) command line interface available

f) Monitoring via GUI

5) Live Migration & High Availability Cluster

Proxmox VE High Availability Cluster enables the definition of high available virtual servers. With the implementation of a cluster you can balance the workload on different hosts, increasing availability of virtual machines.If a virtual machine or container (VM or CT) is configured as HA and the physical host fails, the VM is automatically restarted on one of the remaining Proxmox VE Cluster nodes. In case of hardware maintenance, you can move the virtual machines on another node without any downtime, (or limited downtime).

we can move running virtual servers from one physical host to another without downtime.

For KVM based containers

The migration of a virtual machine, running from one physical host to another, is done without any interruption. In order to use the live migration, all virtual disks must reside on shared storage, between hosts, as a SAN or NAS.

For OpenVZ containers

It’s possible to achieve containers migration without downtime, even using local storage, so shared storage is not required. (No San or Nas)

6) ProxMox VE Private Clouds from Hivelocity

Hivelocity offers highly scalable single tenant Private Cloud solutions on several IaaS platforms including ProxMox VE, OpenStack, VMware, HyperV and more. You can find a description, pricing and demo videos of each of these solutions at https://www.hivelocity.net/products/private-cloud/.

Feel free to open a live chat or give us a call if you would like to discuss which of our Private Cloud solutions, if any, might be best for your business. Every Private Cloud we deploy starts with our team of cloud experts consulting with your team. Together we decide what solution best meets your needs and budget.

The post What is Proxmox VE? appeared first on Hivelocity Hosting.

Docker is an open source platform for developers and system administrators to build, ship, and run distributed applications based on Linux containers.

At its core, Docker is basically a container engine which uses Linux Kernel features such as namespaces and control groups. This allows it to create containers on top of an operating system and automate application deployment on the containers.

In addition to providing a light weight environment to run the application code, the use of containers allow users to package up an application with all of the parts it needs to operate correctly. By including libraries and other dependencies, applications can be transferred from one machine to be easily run on another.

Because Docker makes use of the Linux kernel housed on the machine it’s running on, regardless of any differences or customized settings, so long as any non-native elements are included within the package, your applications will run on any Linux machine. This means developers are more able to focus on coding without having to build around a specific system.

What are Docker’s Features?

The following is a list features that make Docker unique:

Features

1. An isolated, rapid framework.
2. An open source solution
3. Cross cloud infrastructure
4. Moderate CPU/memory overhead
5. Fast reboot

Components

Docker is made up of the following major components:

1) Docker Daemon

The Docker daemon is a service that runs on a host machine and acts as the brains of the system. A user can’t directly interact with the daemon. By entering commands into the Docker client, these commands are translated and sent over to the daemon to execute them.

2) Docker Client

Docker client is the primary user interface which helps users interact with the Docker daemon. It processes the commands from the user and communicates back and forth with the daemon in order to execute those commands.

3) Docker Images

These are read-only templates that help launch Docker containers. A Docker image can be of CentOS operating system with Apache and your web application installed. These images are then used to create the Docker containers. Docker allows users to build new images or you can simply edit and update the images.

4) Docker Registries

Docker registries hold the Docker images. These registries are either public or private stores where you upload or download images. The public Docker registry, also called Docker Hub, provides a huge collection of existing images for use. You can easily edit and update the images as per your requirements and can upload them to other registries.

5) Docker Containers

Each Docker container is an isolated & secured application platform which holds everything that is needed for an application to run. You can perform run, start, stop, migration, and delete operations on a docker container.

Popular Links

Looking for more information on Docker? Search our Knowledge Base!

Interested in more articles about Virtualization? Navigate to our Categories page using the bar on the left or check out these popular articles:

• What is Proxmox?
• What is OpenStack?
• How to Use RSYNC with Cloud Storage

Popular tags within this category include: Proxmox, OpenStack, Cloud Storage, and more.

Don’t see what you’re looking for? Use the search bar at the top to search our entire Knowledge Base.

The Hivelocity Difference

Seeking a better Dedicated Server solution? In the market for Private Cloud or Colocation services? Check out Hivelocity’s extensive list of products for great deals and offers.

With best-in-class customer service, affordable pricing, a wide-range of fully-customizable options, and a network like no other, Hivelocity is the hosting solution you’ve been waiting for.

Unsure which of our services is best for your particular needs? Call or live chat with one of our sales agents today and see the difference Hivelocity can make for you.

The post What is Docker and What are Its Features? appeared first on Hivelocity Hosting.

Openstack was actually founded in July 2010 with the vision to provide open source software that enables any organization to create and offer cloud computing services running on standardized hardware.

Components of OpenStack

Openstack is a collection of many different mobile parts, as it is open source cloud computing software. Any one can add additional components to openstack to optimize their openstack based cloud infrasructure and to meet their needs. However, the openstack community has collaboratively identified some key components that are part of the core of Openstack which are distributed as components of any openstack system and officially maintained by the Openstack community.

a) Nova

Nova is the primary computing engine behind OpenStack. This component allows the end user to create and manage large number of virtual servers using the machine images. It is the brain of the Cloud. OpenStack computes provisions and manages large networks of virtual machines.

b) Swift

Swift is a storage system for objects and files. It overrides the traiditional way of a referring to files by their location on a disk drive. Users can instead refer to a unique identifier referring to the file and let OpenStack decide where to store this information. This component stores and retrieves unstructured data objects through the HTTP based APIs. This makes scaling easy, as users don’t have to worry about the capacity on a single system behind the software. Due to its data replication and scale out architecture this component makes sure that data is backed up in case of failure of a machine or network connection.

c) Neutron

A networking component of Openstack which helps to ensure that each of the components of an OpenStack deployment can communicate with one another quickly and efficiently. It is a pluggable, scalable and API-driven system for managing networks which provides the networking capability for OpenStack.

d) Horizon

This component provides a web-based portal or an interface to interact with all the underlying OpenStack services. It is the only graphical interface to OpenStack. Its a Dashboard which helps system administrators take a look at what is going on in the cloud, and to manage it as needed.

e) Cinder

A block storage component which provides persistent block storage to running cloud instances or servers. The flexible architecture of Cinder makes the tasks easy for creating and managing block storage devices.

f) Keystone

This component provides a central directory of users mapped to the OpenStack services where all of the users of the OpenStack cloud are mapped against all of the services provided by the cloud which they have permission to use. It is used to provide an authentication and authorization service for other OpenStack services.

g) Ceilometer

This component monitors the usage of the Cloud services of each user and performs the billing task accordingly. It keeps a verifiable count of each user’s system usage of each of the various components of an OpenStack cloud.

h) Glance

This component stores and retrieves the virtual machine disk image. Glance allows these images to be used as Operating System templates when deploying new virtual machine instances.

i) Orchestration Heat

An orchestration component of OpenStack, which helps to manage the infrastructure needed for a cloud service to run. This component manages multiple Cloud applications through an OpenStack-native REST API and a CloudFormation-compatible Query API. It allows users to store the requirements of a cloud application in a file that defines what resources are necessary for that particular application.

j) Trove

A Database as a Service component for OpenStack . It allows users to quickly and easily utilize the features of a relational database without the burden of handling complex administrative tasks such as deployment, configuration, patching, backups, restores, and monitoring.

The post What is OpenStack? appeared first on Hivelocity Hosting.

This how to will provide you instructions for mounting your cloud storage to your CentOS, RHEL or Fedora system as a usable drive. This can be very useful and helpful when performing tasks and/or moving/manipulating files to and from your cloud storage device.

Retrieve your cloud storage information

First login to my.hivelocity.net and navigate to Services & Hardware.

Next, click the Cloud Storage button at the top. Once you are in the Cloud Storage page you will see Login Details. Please copy these details safely or keep this tab open as you will need these credentials later.

Now your ready to begin configuring the server

Use an SSH terminal application like Putty or another OpenSSH client to connect to your server with the root credentials provided in your servers welcome letter.

You will need:

• Server IP address
• Server SSH port (22 is default — if you see Connection refused error, you are using the wrong SSH port)
• User: root or sudoer user
• Password

If you are unsure what your credentials are, please request a password reset through your my.hivelocity.net portal by issuing a ticket to general support or email us support@hivelocity.net

1. Install SSHFS

Perform the following while connected to your server via SSH terminal application.
yum install sshfs

2. Create mount directory

mkdir /cloud-storage

3. Mount remote filesystem

Replace yourusername with your cloudstorage login username
Replace cloudstoragedomain with cloud storage IP or domain (cloudstorage1.hivelocity.net or cloudstorage2.hivelocity.net etc) found within your my.hivelocity.net -> Cloud Storage information sshfs yourusername@cloudstoragedomain:/ /cloud-storage Example line would something like: sshfs caccount_1077@cloudstorage1.hivelocity.net:/ /cloud-storage

4. Check the new mounted drive contents

Check to make sure the mount was created successfully df -h You should now see the mount listed at the end

Also check to see if your storage contents can be listed ls -lh /cloud-storage

5. Configure the system to remount upon reboots

nano /etc/fstab Navigate to the bottom of this file and insert the mount line: sshfs#yourusername@cloudstoragedomain:/ /cloud-storage fuse defaults 0 0

6. Unmounting the drive

If you need unmount the drive at any time, you simply need to perform the following. umount /cloud-storage

If you thought that was helpful, check out this article on How to use RSYNC with cloudstorage from our Impressive Support staff

Back to Top

The post How to mount your cloud storage drive on your CentOS, RHEL or Fedora systems appeared first on Hivelocity Hosting.

How to Use the RSYNC Command to move files and folders from server to The Storage Cloud

The RSYNC Command is used in a Shell to move files/folders from server to server over the internet. The RSYNC Command can come in useful when you are just needing to back up to a Cloud Storage Device from your server or even transferring to a new server. The following tutorial will explain the steps you need to take to help move your important information into a cloud storage device.

First off you want to start a new SSH Terminal that is connected to your server.

Now that we are in our server we can create a package which contains the files/folders needing to be backed up:

2) In this case, we have a Folder called “backup” in the root directory of the server which has files Test1.txt, Test2.txt, Test3.txt, and a subdirectory called “data” that will need to be archived

CODE: tar -zcvf backup-4-2-2015.tar.gz /backup

Now, The Above command will archive the whole “backup” folder we specified and place it inside of the root directory (if you’re running it outside of the folder specified) – so it now it is located below:

CODE: /root/backup-4-2-2015.tar.gz

Now, that we have created the backup it is time to RSYNC to our cloud storage device:

You Will need your My.Hivelocity.Net Login for this Step.

1) Login to Your My.Hivelocity.Net Portal and Navigate to: Services & Hardware > Cloud Storage
This will locate your username and password to login to your cloud storage.

2) Now that we have our Login Details We can go ahead and start the transfer:

CODE: rsync -avciz /root/backup-4-2-2015.tar.gz gfreeman_11032_a34a@cloudstorage3.hivelocity.net:/home/gfreeman_11032_a34a/backup

NOTE: This is the PUSH Command to push it from your Local Server to the Cloud

3) Once the command is ran you will receive this result:

NOTE: The Password is the password found in your my.hivelocity.net portal

4) And so now that it has completed pushing the information over to the cloud you may refresh your my.hivelocity.net portal page and you will see your new folder:

You have now completed Backing Up to The Cloud Via RSYNC.

The post How to use RSYNC with CloudStorage appeared first on Hivelocity Hosting.

To manually deliver those mails refer the following steps :

a.Login the server as root.

b.Fire the following command:-

exim -d9 –qff

Note:-After firing the above command,the server load would get increased drastically,

since the mails in the queue will be delivered, keep a watch on it.

The post How do I manually deliver all of the mail in my VPS mail queue? appeared first on Hivelocity Hosting.

The post Starting and Stopping Your Virtuozzo VPS appeared first on Hivelocity Hosting.

The post Connecting to Your Virtuozzo VPS via SSH appeared first on Hivelocity Hosting.

The post Mounting and Unmounting Your Virtuozzo VPS in Repair Mode appeared first on Hivelocity Hosting.