3650 Research Paper

snottysurfsideΔιακομιστές

9 Δεκ 2013 (πριν από 3 χρόνια και 10 μήνες)

199 εμφανίσεις


3650 Research Paper


For


Proxmox VE


Version 1.0 approved



Author:

Ryan Holladay

Mentor: Anthony Kombol

University of N
orth
C
arolina

Charlotte



21 July 2011


2


Author:


Ryan Holladay




Contact Information:




Telephone:

(704) 425
-
8802




Email:


ryanholladay@gmail.com

(Permanent)






rphollad@uncc.edu

(University)


Mentor:



Anthony Kombol




Contact Information:




Telephone:

(704) 687
-
8194




Email:


tkombol@uncc.edu

(University)


Research Completed for:

Department:

College of Computing and Informatics




College:

Software Information Systems




Location:

Woodward Hall 311 (Lab)






Woodward Hall 302 (Lab)


Date of completion:

10 August 2011



3


Table of Contents

Abstract

................................
................................
................................
................................
................................
.

4

Introduc
tion

................................
................................
................................
................................
..........................

5

Body of Work

................................
................................
................................
................................
........................

7

Initial Meetings

................................
................................
................................
................................
.................

7

Installation

................................
................................
................................
................................
........................

8

Creation

................................
................................
................................
................................
..........................

10

Migration and problems

................................
................................
................................
................................
.

11

In summary

................................
................................
................................
................................
.....................

12

Works Cited
................................
................................
................................
................................
.........................

13

Appendix A

................................
................................
................................
................................
..........................

15

My Work Journal

................................
................................
................................
................................
.............

15

Appendix B

................................
................................
................................
................................
..........................

30

My screen caps

................................
................................
................................
................................
...............

30

Creating VMs

................................
................................
................................
................................
...............

30




4


Abstract


The purpose of this project was to investigate the use of Proxmox VE in a multiple server
environment.

The major problem was to deploy Proxmox VE to the servers in Woodward 311.

The
other major focus of this project was to see if the Proxmox VE servers could support multiple Virtual
Machines and their migration.

The main purpose of studying Proxmox VE

w
as to see if these problems
could be answered.

In accompaniment with the research going on throughout the project, another
major aim was to create lab write ups for future students to follow and complete work.

Throughout the
research project I made sure
to use my knowledge of the Internet and other technical sources to seek
answers. Along with the use of the Internet, I used the help of my mentor A. Kombol and close
colleague J. Mullis to seek answers.

The major results for the project are that Proxmox
VE is a fairly easy
to use tool for creating multiple servers, that there may be a network issue with the hardware in
Woodward 311, that Proxmox VE may have networking flaws that don’t allow for the proper transfer of
data, and the creation of Virtual Mach
ines through Proxmox VE is a very easy process.

Although the
problem regarding the network speed was never truly pinpointed by A. Kombol, J. Mullis, or me the
overall thinking is that Proxmox VE
was causing the loss of speed. Aside from the slight speed
question,
the Proxmox VE software proved to be a rather powerful tool and could use some further research to
determine the full potential of the software in an academic setting.




5


Introduction


This paper will follow a standard research paper format. Fol
lowing the
Introduction

will be the
Body of Work
,
References
, and
Acknowledgements
. All of this will be followed by two appendices:
Appendix A


My Work Journal

and
Appendix B


My Screen Caps
. At the very end of the paper, I have
provided rough copies
of the lab write ups that my potentially be used later by future students taking a
course in server virtualization.

Throughout this research paper many technical terms and jargon will be used to describe portions of
the project.

Listed below are the terms

defined in laymen’s by the author.




Virtual Machine

or
VM

is an isolated operating system installation that runs within a normal
host while acting as an individual computer.



Virtual Environment

o
r

VE

is the isolated area that individual or multiple VMs

can run and
generally acts as a server environment.




OpenVZ

is a form of container virtualization used by Proxmox and acts as a virtual container for
certain types of virtual appliances.




Kernel
-
based Virtual Machine

or
KVM

is another form of container
virtualization used by
Proxmox and various other programs that allow for virtualization.




Windows Secure CoPy
or
WinSCP

is a program used to transfer files between two machines
through an IP connection.

Internet Protocol or IP is a protocol used for tran
sferring information
across a network.




ISO image

or
ISO

comes from the International Organization for Standardization and is an
archive file (disc image of a DVD
-
ROM or CD
-
ROM format) that often times includes the
information for an operating system.




Secure Shell
or
SSH

is a network protocol that allows for the exchange of data through a secure
channel between two machines that are networked.


6




PuTTY

is an open source program used for

SSH, Telnet, other networking protocols using a
client
-
based login s
ystem.

The Proxmox environment was developed by Proxmox Server Solutions GmbH as a means to
provide a simple
-
to
-
us
e virtual server. In doing so Proxmox aims to provide pre
-
built appliances, an
installation manager that can be run through using mouse
-
click
s, and a wide selection of products
for the use in the enterprise world.

Being that Proxmox VE is an open source project, it is licensed
under GPLv2.


A. Kombol and I discussed this as a potential project because he had heard “buzz” about
Proxmox througho
ut the Internet. He mentioned that he had also seen several web
-
based
television episodes online that were dedicated the ease
-
of
-
use of Proxmox.

He suggested that I
research Proxmox first through these web
-
based television episodes on the website Hak5 an
d then
through research of the individual Proxmox site.

Upon doing basic research, I came back to A.
Kombol ready to discuss the potential project.


A. Kombol charged me with the responsibility of testing the Proxmox VE software on our
servers in Woodward

311 throughout the du
ration of Summer 2011 Session 2 (running
approximately from 7 July 2011 until 9 August 2011).

The parameters of the project would be to
first set up the Proxmox software on the lab servers, second would be to configure the servers wi
th
the proper amount of VMs, and third would be to test the migration potential between multiple
servers.

By the end of the project the goal was to have tested the software, have a complete
research paper write up, and provide lab write ups for potential
future students taking a course
related to virtual server environments.



7


Body of Work


This section is designed to shed light on the work completed throughout my research. This will
take the reader through the initial meetings between A. Kombol and me, t
he installation of the
software, the creation of the VMs, and the problems that were run into along the way.


Initial Meetings


I met with A. Kombol because I was in need of a project to count for a 3hour course and we
began to brainstorm on topics that I
was interested in. Through our conversation Kombol determined
that he would like me to look at a piece of software that he had heard a lot about. I let Kombol know
that I was up to the challenge and would gladly test this software.


After some research
on my part that included watching two different web
-
based television
episodes through the website Hak5 and some research through the Proxmox website, I came to Kombol
with my base
-
knowledge.


Kombol determined that for the project he would like me to insta
ll several VMs on the servers in
Woodward 311. He suggested VMs consisting of an Ubuntu client, Windows 7 client, Windows XP
client, Debian client, CentOS client, Debian Apache server, Debian mail server, Windows 2008 server
with IIS, CentOS DNS server, a
nd a CentOS FTP server.

He and I talked about seeing how the servers
would react with one another once they were up and running. Along with checking

on

the running
capabilities of the machine

and

testing the migration functions of the servers
, I would ne
ed to test

the
ability to control the migration upon catastrophic failure.


Kombol and I continued to meet throughout the course of my research but it was the initial
meetings that set the precedence for my work. Along with our discussions about the softw
are itself,
Kombol instructed me that I would need to record my work and come up with potential lab write ups for
other students to follow if a course were to be created from my work.

8


Installation


The installation of the Proxmox software was a fairly easy

process. Proxmox offers its open
-
source software through its website and can be downloaded by anyone. I downloaded the Proxmox
software and using my personal knowledge of computing, I burned the ISO to a CD
-
ROM.

After doing so
I took my software in wit
h me to school and started the installation process on the first server.


Following the simple mouse
-
click installation steps, I worked through the installation:

1.

Click “I agree” to the Proxmox License Agreement

2.

Entered “United States of America” for Countr
y

3.

Selected the Eastern/NYC (
-
5 GMT) for Time zone

4.

English for Keyboard Layout

5.

Password and Confirm I set to “root49”

6.

Entered
rphollad@uncc.edu

for E
-
Mail

And then came the important part for the ins
tallation process
, the Hostname naming and IP
configuration. At this point I asked Kombol for help because I wanted to make sure that my naming
standards adhered to his liking and potential needs for the future.

o

Hostname (FQDN):

proxmox01.hogwarts.lab

o

IP Address:


10.10.10.2

o

Netmask:


255.255.0.0

o

Gateway:


10.10.10.1

o

DNS Server:


10.10.10.10

This would become important later for the naming of the other servers in our cluster and would become
important to keep the lab name different from the one that already exists i
n Woodward.

9



Any time that I made a change or created something related to the server, I made sure that I
noted it on the white board in the lab which can be seen in my screen caps in
Appendix B
.


During the setup and installation process Kombol also had m
e configure the front LCDs on the
servers to read personally defined messages. This can be done on our DELL servers by going through the
setup after the initial boot.

1.

During boot, press F2 to enter BIOs setup

2.

Scroll down to “Embedded Serer Management” and

press Enter

3.

Select “Front
-
Panel LCD Options” and use the left and right arrow keys to select “User
-
Defined String”

4.

Select “User
-
Defined LCD String: Line 2” and enter up to fifteen alphanumeric characters
and press Enter.

5.

Escaped out of the setup after mak
ing sure to Save Changes.

6.

Upon a reboot the Front
-
Panel LCD should display the message set

Aside from the installation of the Proxmox software on the individual servers, the only other thing that
required doing in the lab to get ready for the work ahead wa
s to clean things up and set up the servers
on the switch. The switch that we were using in the lab was a CISCO 48
-
port switch with Giga
-
bit
potential. I made sure that the power was on with the switch and plugged all the servers in through
their individ
ual Giga
-
bit eth0 connections.


After connecting the servers through the switch, I could access each one of them through the
Proxmox web
-
based GUI. This GUI gave me administrative control over the servers and gave me the
options that I would need to insta
ll and manage multiple VMs.

10


Creation


The next step in the process of my research was to create multiple virtual machines. To do so, I
made sure that I retrieved ISOs of the individual system builds that I would need and copied them over
to a portable
hard drive. I used the portable hard drive and a WinSCP connection to transfer the ISO
files over to the servers:

o

For ISO (KVM) usage the files needed to be placed in:

o

/var/lib/vz/template/iso

o

For OpenVZ usage the files needed to be placed in:

o

/var/lib/vz/template/cache

Although for this project, I tended to stay away from OpenVZ considering that the information that I had
read on the Proxmox forums suggested that OpenVZ appliances tended to have problems running
traditional operating systems.


Once I had all of my ISO files transferred over onto the servers I started the VM creation phase
of my project. Through the Proxmox web
-
based GUI I could create a VM in a matter of seconds. After
creating them I was required to run through the VNC to com
plete the installation of the machines. By
the end of the creation and installation process my servers and VMs were configured as such:

10.10.10.2/ proxmox01





10.10.10.3/ proxmox 02

VM#


VM Name




VM#


VM Name

101


Ubuntu_Client




106


Debian_Server_
Apache

102


Win7_Client




107


Debian_Server_Mail

103


WinXP_Client




108


Win2008_Server_IIS

104


Debian_Client




109


Cent_Server_DNS

105


Cent_Client




110


Cent_Server_FTP

11



Each VM had its own configuration and could be run simultaneously with the
other machines up
and running. The web
-
based GUI seemed to show that the servers could handle the work load just fine.
This however was with just two servers up and running. The control of the servers came from the
laptop that I was using in the lab tha
t I used to work through the web
-
based GUI and would rarely work
from the KVM controller on the server rack.


Migration and problems


Considering that the creation of the VMs was fairly simple process, I figured that migration and
other functions related t
o server configuration would be simple.


The first problem I ran into when dealing with the servers was when I was creating a master and
various nodes for the cluster configuration. Without an NTP to control server times, the individual
servers require th
e times to be set individually through a time set terminal command. This sort of
command can only be run through the KVM terminal on the server rack or through program like PuTTY
that allows one to login to the system remotely.


This sort of time configur
ation became a problem considering that I liked to shut down the
servers during the weekend to ensure that my work would not be compromised. However, in hindsight
the shutdowns were causing more problems than good.

Although in the future the creation of
an NTP
server would fix this problem regardless. Still I had questions regarding the server timings considering
that they would be set one day and then would be off by a couple of minutes or in one case were off by
an hour or two.

This did not seem right

to me considering that these servers were running internal
clocks and should not be subject to such great time variations.


The second problem that I ran into regarding the servers occurred before the machines were
formed into a cluster. I was trying to
migrate one of the VMs to another one of the servers. I noticed
12


that I was getting approximately 4.5MB/s. This sort of speed seemed absolutely preposterous
considering that all of the servers were running Gigabit connections and were running through a sw
itch
that supported Gigabit traffic.


This problem plagued both A. Kombol, J. Mullis, and me throughout the final weeks of the
project. At the suggestion of J. Mullis, I changed all the wiring out of the servers and the switch. I also
changed out the swi
tch for another switch with Gigabit capability.

After several restarts and hardware
changes I noticed no changes in speeds. The transfer speeds that I had been receiving seemed to be
related to the server hardware itself or the Proxmox software.


At the
request of Kombol, I went ahead and used the TCP Dump feature that the Proxmox
software provided to run some tests on the connections. I also attempted to install Wireshark to check
the network traffic. However, I am not familiar with how either one of t
hese programs works so I was at
a great disadvantage.

After conferring with Kombol on this matter, he instructed me to push no further
considering that I had reached the ceiling of my knowledge.


The question still remains as to why the network traffic sl
owed to as slow as it did and will be a
question that is better

to be

left
to be
answered by future researchers.


In summary


Through the duration of the project, I installed the Proxmox software on all four servers in the
Woodward 311
lab;

I created multi
ple VMs, and

worked through migration and configuration.

I ran into
some problems throughout my work, but found some work
-
rounds through surfing the internet.

I have
tested my skill with VMs and with server management. I have learned what my current lim
its are and
what I would need to do to improve those limits.

And ultimately I have worked for five weeks on a
pretty interesting project that has helped me understand my potential.


13


Works Cited

Griffon's IT Library
. (n.d.). Retrieved 2011, f
rom Setup your ProxmoxVE: http://c
-
nergy.be/blog/?p=393

Hak5
. (n.d.). Retrieved 2011, from http://hak5.org/

Kombol, A. (n.d.). (R. Holladay, Interviewer)

Mullis, J. (n.d.). (R. Holladay, Interviewer)

PVE.Proxmox.com/Wiki
. (n.d.). Retrieved 2011, from Main
Page: http://pve.proxmox.com/wiki/Main_Page

UnixInstallBuilds
. (n.d.). Retrieved from Wireshark.org:
http://www.wireshark.org/docs/wsug_html_chunked/ChBuildInstallUnixInstallBins.html


14


Acknowledgements

I would like to thank Mr. Anthony Kombol for all
owing me to work on this project. I would like
to also thank him for his time and instruction throughout the project. Without Mr. Kombol’s instruction
in previous courses a lot of this work would not have been possible.

I would also like to thank Mr. Ju
stin
Mullis for his help in answering questions that I had throughout my project regarding networking and
networking configuration. Without Mr. Mullis’ help I would have had to continually bother Mr. Kombol
for his valuable time. I would like to thank bo
th gentlemen for helping me work through my project.


15



Appendix A

My Work Journal

Tuesday 05 July 2011

Met with Kombol and discussed the project.



Proxmox Servers (2+) that will run multiple virtual machines

o

Windows



Server



7

o

Linux



Ubuntuu



Debian



CentOS

Disc
ussed installing Proxmox on multiple servers in the lab.

Need to clean up the lab on Thursday.

Install Proxmox on the systems in the lab, and don’t forget that the drives will need their RAID set
accordingly.


Thursday 07 July 2011

Once in Proxmox web
interface:


Application Templates > Local | Download


ISO images > upload file

Can shutdown / restart through the web gui

Need to work on getting images up through the machine. See how to install VMs through the input.


Might need to burn iso to CDR not t
hrough dvd

As pretty as the pixelated Dell logo is, another option is to label your servers using this LCD. While this
procedure is no doubt documented somewhere, our documentation got relocated somewhere shortly after
delivery. We still haven't found it.
So here's how to do it.

16


1.

During boot, press F2 to enter BIOS setup. Scroll down to "Embedded Server Management" and
press Enter.

2.

Select "Front
-
Panel LCD Options" and use your left and right arrow keys to select "User
-
Defined
String" from the available optio
ns (the other options being "Default" and "None").

3.

Select "User
-
Defined LCD String: Line 1" and type in up to five alphanumeric characters. Press Enter.

4.

Select "User
-
Defined LCD String: Line 2" and type in up to fifteen alphanumeric characters. Press
Enter
.

5.

Escape out of the setup, making sure to Save Changes. After a reboot, you'll bask in the neon blue
glow of your newly customized LCD marked servers.


Tuesday 12 July 2011

Went ahead and burned:


Debian


Ubuntu


Windows 7


Windows XP

To CD and DVD only to

find out that Proxmox requires the ISO present for installation or installation from a
local location.


Did find out that with Proxmox up and running, I can go ahead and transfer over various ISOs of what I would
like each machine to run. The servers sto
re the ISOs in /var/lib/vz/template/iso and for OpenVZ in
/var/lib/vz/template/cache


Set up
winscp

on my machine so that I can ftp into the servers


I am going to go ahead and create the VMs on each of the machines for the corresponding client or server
applications. Using the clients first because I can’t remember exactly what Kombol wanted of each one.

10.10.10.2/

101 Ubuntu_Client


24G

512MB

102 Win7_Client



24G

1024MB

103 WinXP_Client


24G

1024MB

17


104 Debian_Client


32G

512MB

105 Cent_Client



32G

51
2MB

106 Debian_Server_Apache

32G

512MB

107 Debian_Server_Mail

32G

512MB

108 Win2008_Server_IIS

32G

512MB

109 Cent_Server_DNS


32G

512MB

110 Cent_Server_FTP


32G

512MB

Will duplicate on 10.10.10.3/

I have also started to document the process through the usa
ge of screen captures and I am saving them in
various locations so that later I can update the whole lab. Kombol has given me space in Moodle as well to
upload documentation.


Thursday
14 July 2011

Using WinSCP to move over ISOs to the server1:


Still nee
d working server 2008 iso and non
-
tar Cent version

Checking the server to see is through
ls

I can see the actual files, which I can. Currently showing
en_windows_7_professional_x86_dvd_x15
-
65804.iso.filepart

and
debian
-
6.0.2.1
-
amd64
-
CD
-
1.iso

Found out thr
ough research that Proxmox VE uses a version of TightVNC:

http://forum.proxmox.com/threads/612
-
External
-
VNC
-
viewer

Reinstalling the VMs using the right ISOs

Going to have to restart m
y machine after installing windows xp VM, my os is hating me right now.

**Make sure that when creating VMs that for the installation click on the dropdown to select the ISO.

Going to try to install Cent via Applications

Completing dumping the ISOs onto ser
ver2


Tuesday
21 July 2011

Setting up the servers on proxmox1


Taking screen caps of process for lab creation


18


**Start lab write ups for VM creation Sunday**


**Start research paper write up Sunday**


Work on server and node creation for Tuesday:


Make 01
server


Make 02 node

Make sure to shadow all the VMs and start working on the systems work up for permissions and settings

Win2008 > Admin PW: Unccroot49


Configure the DNS and FTP VMs


Configure domain etc.


Thursday 23 July 2011

Worked on getting machine
s up and running through the KVM

Working on getting the machines connected through the switch

Research the switch


Tuesday 26 July 2011

Connected machines through switch in lab, started work on the connection process.


See if servers can connect to one a
nother through switch


Finished work on lab 1 and 2, completed and uploaded to moodle


Will finish lab 3 and 4 on Thursday to prepare for the rest of the lab

19



Continuing working on research paper for final deadline


Need to continue to take screen caps


Will need to take pictures of server environment for the final research paper write up


Thursday 28 July 2011

Creating a master and node:

Install Putty

Migration process seems to take a good amount of time, clocking it at around 10minutes


Migration has
taken upwards of 30minutes


Proxmox02 is showing the process as complete while Proxmox01 is still showing that the process is
still working through.


Transferring at 4.81MB/s


Might want to compress the hard drive size for labs

Need to try to migrate while

up and running and see how long it takes.

Setup all 4 servers and they are up and running, need to add the other’s to the node

Making sure to work on the time settings

Wish I knew how to set up an NTP!


USAGE: pveca
-
l # show cluster status



pveca
-
c # create new cluster with localhost as master


pveca
-
s [
-
h IP] # sync cluster configuration from master (or IP)


pveca
-
d ID # delete a node


pveca
-
a [
-
h IP] # add new node to cluster

Define th
e master

Login via ssh to the first Proxmox VE server.

Create the master:

20


pveca
-
c

To check the state of cluster:

pveca
-
l


Login to server1

Setup your ProxMox VE Infrastructure


Part 3

Date Posted: April 5th, 2010

Written by admin

Category:

PROXMOX VE

Overview

As mentioned in my previous posts, PROXMOX VE (PVE) c
an be run

as a cluster
. The cluster configuration is
based on one node being the master and other nodes being the slaves .


By implementing a cluster, you will be able to balance the workload on several hosts and you will be able to
increase the availabil
ity of your virtual machines.


With a PROXMOX VE Cluster, you will be able to perform
“live migration” even if you do not have shared storage.


In case of hardware maintenance, you will be able
to move “on the fly” the virtual machines on another node with

no downtime (or limited downtime).


Now what’s happens if a cluster node fails ?


If you haven’t implemented any shared storage, you might have
no more access to some of your virtual machines. The PROXMOX VE does not migrate your VM from one
node to anot
her if a crash occurs. I haven’t tested yet the situation if a shared storage infrastructure or using
the DRDB technology.At the moment, we will not dive so deeply in the product and the clustering features.
We will come back to these topics in some future

posts.


In order to build t
he PVE Cluster,

we need to install 2 PROXMOX VE servers. Follow the Installation procedure
described on

Part I
,


In our example, the PROXMOX VE hosts will have the following settings :


HOST 1





Hostname : NODE1.Study.lab



IP Address : 192.168.1.10



Subnet Mask : 255.255.255.0

HOST 2





Hostname : NODE2.Study.lab



IP Address : 192.168.1.11



Subnet Mask : 255.255.255.0

21


SETTING UP A 2
-
NODE PROXMOX VE CLUSTER

You will see that building a clu
ster with PROXMOX VE is really simple. However, you have to know that the
setup cannot be performed through the web interface (at the moment). You will need to use the command
line.


You will need to logon locally on the console of each PROXMOX VE hosts an
d perform the following
tasks or you can use your favorite ssh client tool (I’m using Putty.exe) in order to remotely connect to your
PROXMOX VE hosts and perform the configuration steps.


Let’s start !


Important Note

:


Before trying to create the clu
ster, you will need to ensure that both PROXMOX VE Hosts are in sync. You
have to check that both hosts have the same time. If there is a time difference between the two hosts, you
will get error messages within your console. If the time is not identical b
etween the hosts, you might end up
with the following error when creating your cluster.


Ticket authentication failed


invalid ticket ‘root::root::1252946231::f1292eb0564a15169aaf30e36
1382247fccf718c’


Step 1 : Check time settings on

both nodes




In

part 2
, we have shown you how to check the configuration of your system. Let to this again.




Open your favorite browser and login into the Web interface on

node 1 and node 2



On the left menu, in the
Configuration section, click on system





click on the Time tab





Check that the Time is identical on both hosts

22


If they are not, you can use the following command line (through putty or console) to set the correct time on
the hosts


date +%T
-
s
“hh:mm:ss”

(ex. : date +%T
-
s”10:15:53

)



Note: We recommend to use a NTP server in order to synchronize your clock automatically.


you can set the
ntp server by editing the /etc/ntp.conf file.


Step 2 : Go to your master Node and create your cluster


In this demo, I’m assuming that the Node1 will be the master node of the future cluster I’m building up






Logon into the console or use putty to node1



Type the following command pveca

help.

pveca is the command line utility that will be used to
create

the cluster.

As you can see, there not a lot of options
-
>meaning quite simple to use







To create the cluster, you will need to type the following command in the console,


pveca
-
c





If everything went correctly, you will see the following output



Step 3 : Go to your slave


Node and add it to


your cluster




Login into your slave server (in this demo node2) through the console or using putty.exe



To add the server to the cluster, you simply type the following command
pveca
-
a
-
h <%IP address of
t
he Master Server %>

23






You will be asked if you want to continue the connection. Type

yes. You will then need to provide
the password for the master node.

At the end of the procedure, you will have a PVE Cluster





As a final step, you can type pveca
-
l

to check the status of your PVE Cluster



That’s it ! Yes, you have typed in 3 commands and you have a working PVE cluster. That’s cool !


So, let see what’s has changed in the web interface !


Managing your PVE Cluster through the Web Interface

In or
der to manager your cluster, you should always connect to the master node. Even you are able to
manage both nodes, some operations can be performed only from the Master Node.

For example, I’ve tried
to download an appliance to the slave node and had a mes
sage error stating that I had no Write access.

If
you login into your console, you can notice on the home page

on the top section that you have the
information about the cluster and status of the nodes.


Note : It’s possible that just after creating the

cluster, you will get a blinking message specifying that nodes
are not in sync.

You will just need to wait a little bit in order to have the nodes to synchronize between each
others.


24




You can click on one of the node in the table and you will be red
irected to the management console of the
node you have selected (see figure below)




In the administration section (on the left menu), you can click on the cluster link and have access to read only
information about your cluster.

you can see the nodes

that are member of the cluster. You can also quickly
check the status and identify the master node from the other nodes.




How to migrate Virtual Machines from one node to another ?

To finish with this post, i want to outline the process to migrate vi
rtual machines from one host to another
one.

For this post, i have download and created an OpenVZ container on my Proxmox VE cluster.

In the VM
Manager section (on the left menu), simply click on the virtual machines link. In the right pane, you will see

the list of the virtual machines (in my

demo, i have only one).

If you click on the red arrow at the corner, you
have a contextual menu where you can select the option

“Migrate”


25




You will be then presented this interface. You have to specify the so
urce node, the target node and the
virtual machine to migrate.

You have two options : you can perform an offline migration or an online
migration. In this demo (and because there is a known bug with openVz container), we will perform an offline
migration.


When you have provided the appropriate information, you can click on the migrate link .




If you migration is successful, you will have an output similar to this one.




Known Issue


If your are performing an online migration for KVM virtual mach
ines, you should normally have no issues and
the live migration will work as expected.

If you are trying to perform an online migration of an OpenVZ
container, the migration will fail and you will get a message error similar to “Failed to suspend containe
r”.


26




This is a known issue with OpenVZ. At the moment, you cannot perform an online migration for OpenVZ.
However, you can still perform an Offline migration. You will get some downtime but I have to say that the
move/migration was quite fast.


****F
ROM
http://c
-
nergy.be/blog/?p=393****



Tuesday 02 August 2011

Messed around with Wireshark

Find reading the output confusing

Not really sure what I am reading when I am looking at the net traffic


FROM:
http://www.wireshark.org/docs/wsug_html_chunked/ChBuildInstallUnixInstallBins.html

2.5.

Installing the binaries under UNIX

Prev


Chapter

2.

Building and Installing Wireshark


Next


2.5.

Installing the binaries under UNIX

In

general, installing the binary under your version of UNIX will be specific to the
installation methods used with your version of UNIX. For example, under AIX, you
would use

smit

to install the Wireshark binary package, while under Tru64 UNIX
(formerly Dig
ital UNIX) you would use

setld
.

27


2.5.1.

Installing from rpm's under Red Hat and alike

Use the following command to install the Wireshark RPM that you have downloaded
from the Wireshark web site:

rpm
-
ivh wireshark
-
1.7.i386.rpm



If the above step fails

because of missing dependencies, install the dependencies first,
and then retry the step above. See

Example

2.3, “ Installing required RPMs under Red Hat
Linux 6.2 and bey
ond ”

for information on what RPMs you will need to have installed.

2.5.2.

Installing from deb's under Debian, Ubuntu and other Debian derivatives

If you can just install from the repository then use:

aptitude install wireshark



aptitude should take
care of all of the dependency issues for you.

Use the following command to install downloaded Wireshark deb's under Debian:

dpkg
-
i wireshark
-
common_1.7.0
-
1_i386.deb wireshark_1.7.0
-
1_i386.deb



dpkg doesn't take care of all dependencies, but reports
what's missing.


Note!

By installing Wireshark packages non
-
root users won't gain rights automatically to capture
packets. To allow non
-
root users to capture packets follow the procedure described
in

/usr/share/doc/wireshark
-
common/README.Debian

2.5.3.

Installing from portage under Gentoo Linux

Use the following command to install Wireshark under Gentoo Linux with all

of the
extra features:

USE="adns gtk ipv6 portaudio snmp ssl kerberos threads selinux"
emerge wireshark



28


2.5.4.

Installing from packages under FreeBSD

Use the following command to install Wireshark under FreeBSD:

pkg_add
-
r wireshark



pkg_add
should take care of all of the dependency issues for you.





Thursday 04 August 2011

Locked out of Lab 311

Once connected transferring the isos over to proxmox04, getting an average of 2 MB/s transfer through the
switch


Speeds slowed to 500 KiB/s at one

point

Suggested fixes:


New switch



Dell 2708 switch


New cables

Going to test my direct connection into proxmox03 after proxmox04 is done


Testing direct connection to proxmox03


Noticed on the terminal:



Vmbr0: port 1(eth0) entering disabled state



B
nx2: eth0 NIC cooper Link is Up, 100 Mbps full duplex



Vmbr0: port 1(eth0) entering forwarding state

Had issues connecting into Proxmox03 directly through winscp

Continued to have issue connecting Proxmox03 and 04, each would stay connected for a short ti
me and then
time out.

29


Shutting down all servers and bringing back up using DELL 2176 switch

Connected through the dell switch I am getting approximately 4MB/s

Noticing that NTP needs to be setup. However, in doing so, I don’t have access to the outside wo
rld for doing
so.


/etc/ntp.conf file

date +%T
-
s “hh:mm:ss”

(ex. : date +%T
-
s”10:15:53″)


every time that I try to move an online migration with a system that is still up and running, it crashes
out and will not complete the task.

It appears that
neither of the switches are causing issue

Going to try to install wireshark on the proxmox01 server

FINAL WRITE UP DUE WEDNESDAY!



30


Appendix B

My screen caps

These screen caps go from when I first started all the way until the end. I have included
captions with each
screen cap.

Creating VMs

(The initial installation completion)

31


(The Virtual Machine listing)

(Creating a virtual machine)

32


(A full list of the virtual machines completed)

(Ubuntu VM up and running)

33


(Windows 7 VM setup going through
the completion process)

(Windows XP at the Product Key Registration menu just before completion)

34


(Debian virtual machine during installation process)

(Debian Apache Web Server installation during the process)

35


(Debian Mail Server GRUB! Installation comp
leting)

(Debian Mail Server login screen)

36


(Windows 2008 IIS Server creation)

(Windows 2008 installation beginning)

37


(Windows 2008 up and running)

(Logging in using WinSCP)

38


(Showing the connection established between the host computer and the host
server)

(Transferring the first ISO over through the WinSCP system)

39


(This shows the white board that I was using throughout my work)

40


(Same white board but showing the configurations of the servers)