- •Организация системы доступа пользователей и разработка технических принципов запуска ресурсоемких приложений в распределенной вычислительной среде на основе технологии облачных вычислений
- •Диссертация
- •Глава 1. Классификация распределенных вычислительных сред 15
- •Глава 1. Классификация распределенных вычислительных сред 6
- •2Глава 2. Проблемы доступа пользователей и анализ продуктов для запуска приложений в распределенной вычислительной среде 14
- •Введение
- •Глава 1. Классификация распределенных вычислительных сред
- •Клиент-сервер
- •Основные понятия
- •Метакомпьютинг
- •Кластерная технология
- •Технологии Грид
- •Архитектура Грид
- •Общие задачи Грида
- •Технологии и системы облачных вычислений
- •Основные характеристики Облачных вычислений
- •Особенности облачных вычислений
- •Вызовы облачных вычислений
- •Глава 2. Проблемы доступа пользователей и анализ продуктов для запуска приложений в распределенной вычислительной среде
- •Анализ системы безопасности для распределенных вычислений
- •Системы авторизации Grid
- •Системы авторизации облачных вычислений
- •Анализ Облачных платформ для эффективного построения облачной вычислительной среды
- •Облачная платформа ( eucalyptus)
- •Облачная платформа (OpenNebula )
- •Облачная платформа (Abicloud )
- •Облачная платформа (Nimbus )
- •Анализ безопасности программной интерфейса api для управления ресурсами и сервисами Облачных вычислений
- •Исследование производительности метакомпьютера с единым образом операционной системы
- •Исследование производительности pvm c и без миграции процессов mosix в гетерогенной среде
- •Исследование производительности mpi с и без миграции процессов mosix в виртуальной среде
- •Анализ продукты Globus Toolkit для организации системы доступа пользователей к распределенной вычислительной среде
- •Gridftp – для управления данными
- •Gram – для управления процессами
- •Разработка и исследование системы управления ресурсами Univa Grid Engine в многопроцессорных северах
- •Конфигурация Univa Grid Engine
- •Глава 3. Организация системы доступа пользователей и разработка технических принципов запуска ресурсоемких приложений
- •Разработка системы безопасности грида в систему облачных вычислений
- •Разработка системы управления облачными ресурсами
- •Программный интерфейс drmaa для интеграции программных продуктов
- •Мosix вычислительный кластер на основе технологии облачных вычислений
- •Запуск приложение в распределенной вычислительной среде на основе технологии облачных вычислений
- •Глава 4. Консолидация и интеграция программных комплексов
- •Интеграция mpich2 и uge для запуска параллельных приложений
- •Интеграция uge и Globus toolkit для запуска приложений через drmaa
- •Интеграция системы безопасности Грида в систему Облачных вычислений
- •Разработка программного обеспечения OpenFoam в распределенной вычислительной среде
- •Часть исходного кода программы
- •Заключение
- •Литература
Интеграция системы безопасности Грида в систему Облачных вычислений
На данном этапе настроена аутентификация и авторизация пользователей с помощью сертификатов для системы безопасности. Для создания сертификатов будет использоваться SimpleCA , которая поставляется вместе с Globus Toolkit. Для разработки системы безопасности необходимо выполнить следующие шаги:
globus@ubuntu:/usr/local$ source /usr/local/globus-4.0.8/etc/globus-user-env.sh
globus@ubuntu:~$ /usr/local/globus-4.0.8/setup/globus/setup-simple-ca
WARNING: GPT_LOCATION not set, assuming:
GPT_LOCATION=/usr/local/globus-4.0.8
C e r t i f i c a t e A u t h o r i t y S e t u p
This script will setup a Certificate Authority for signing Globus
users certificates. It will also generate a simple CA package
that can be distributed to the users of the CA.
The CA information about the certificates it distributes will
be kept in:
/home/globus/.globus/simpleCA/
ERROR: It looks like a CA has already been setup at this location.
Do you want to overwrite this CA? (y/n) [n]:y
The unique subject name for this CA is:
cn=Globus Simple CA, ou=simpleCA-ubuntu, ou=GlobusTest, o=Grid
Do you want to keep this as the CA subject (y/n) [y]:
Enter the email of the CA (this is the email where certificate
requests will be sent to be signed by the CA):univa@ubuntu
The CA certificate has an expiration date. Keep in mind that
once the CA certificate has expired, all the certificates
signed by that CA become invalid. A CA should regenerate
the CA certificate and start re-issuing ca-setup packages
before the actual CA certificate expires. This can be done
by re-running this setup script. Enter the number of DAYS
the CA certificate should last before it expires.
[default: 5 years (1825 days)]:
Enter PEM pass phrase:
Verifying - Enter PEM pass phrase:
creating CA config package...done.
A self-signed certificate has been generated
for the Certificate Authority with the subject:
/O=Grid/OU=GlobusTest/OU=simpleCA-ubuntu/CN=Globus Simple CA
If this is invalid, rerun this script
/usr/local/globus-4.0.8/setup/globus/setup-simple-ca
and enter the appropriate fields.
-------------------------------------------------------------------
The private key of the CA is stored in /home/globus/.globus/simpleCA//private/cakey.pem
The public CA certificate is stored in /home/globus/.globus/simpleCA//cacert.pem
The distribution package built for this CA is stored in
/home/globus/.globus/simpleCA//globus_simple_ca_41151393_setup-0.19.tar.gz
This file must be distributed to any host wishing to request
certificates from this CA.
CA setup complete.
The following commands will now be run to setup the security
configuration files for this CA:
$GLOBUS_LOCATION/sbin/gpt-build /home/globus/.globus/simpleCA//globus_simple_ca_41151393_setup-0.19.tar.gz
$GLOBUS_LOCATION/sbin/gpt-postinstall
-------------------------------------------------------------------
setup-ssl-utils: Configuring ssl-utils package
Running setup-ssl-utils-sh-scripts...
******************************************************************
Note: To complete setup of the GSI software you need to run the
following script as root to configure your security configuration
directory:
/usr/local/globus-4.0.8/setup/globus_simple_ca_41151393_setup/setup-gsi
For further information on using the setup-gsi script, use the -help
option. The -default option sets this security configuration to be
the default, and -nonroot can be used on systems where root access is
not available.
******************************************************************
setup-ssl-utils: Complete
globus@ubuntu:~$ ls ~/.globus/
simpleCA
globus@ubuntu:~$ ls ~/.globus/simpleCA/
cacert.pem globus_simple_ca_41151393_setup-0.19.tar.gz newcerts
certs grid-ca-ssl.conf private
crl index.txt serial
root@ubuntu:~# . /etc/profile
root@ubuntu:~#/usr/local/globus4.0.8/setup/globus_simple_ca_41151393_setup/setup-gsi -default
setup-gsi: Configuring GSI security
Making /etc/grid-security...
mkdir /etc/grid-security
Making trusted certs directory: /etc/grid-security/certificates/
mkdir /etc/grid-security/certificates/
Installing /etc/grid-security/certificates//grid-security.conf.41151393...
Running grid-security-config...
Installing Globus CA certificate into trusted CA certificate directory...
Installing Globus CA signing policy into trusted CA certificate directory...
setup-gsi: Complete
root@ubuntu:~# ls /etc/grid-security/
certificates globus-host-ssl.conf globus-user-ssl.conf grid-security.conf
root@ubuntu:~# ls /etc/grid-security/certificates/
41151393.0 globus-user-ssl.conf.41151393
41151393.signing_policy grid-security.conf.41151393
globus-host-ssl.conf.41151393
root@ubuntu:~# source /usr/local/globus-4.0.8/etc/globus-user-env.sh
root@ubuntu:~# grid-cert-request -host `hostname`
The hostname ubuntu does not appear to be fully qualified.
Do you wish to continue? [n]
Aborting
root@ubuntu:~# grid-cert-request -host `hostname`
The hostname ubuntu does not appear to be fully qualified.
Do you wish to continue? [n] y
Generating a 1024 bit RSA private key
.........++++++
.......................................................................................++++++
writing new private key to '/etc/grid-security/hostkey.pem'
-----
You are about to be asked to enter information that will be incorporated
into your certificate request.
What you are about to enter is what is called a Distinguished Name or a DN.
There are quite a few fields but you can leave some blank
For some fields there will be a default value,
If you enter '.', the field will be left blank.
-----
Level 0 Organization [Grid]:Level 0 Organizational Unit [GlobusTest]:Level 1 Organizational Unit [simpleCA-ubuntu]:Name (e.g., John M. Smith) []:
A private host key and a certificate request has been generated
with the subject:
/O=Grid/OU=GlobusTest/OU=simpleCA-ubuntu/CN=host/ubuntu
----------------------------------------------------------
The private key is stored in /etc/grid-security/hostkey.pem
The request is stored in /etc/grid-security/hostcert_request.pem
Please e-mail the request to the Globus Simple CA univa@ubuntu
You may use a command similar to the following:
cat /etc/grid-security/hostcert_request.pem | mail univa@ubuntu
Only use the above if this machine can send AND receive e-mail. if not, please
mail using some other method.
Your certificate will be mailed to you within two working days.
If you receive no response, contact Globus Simple CA at univa@ubuntu
root@ubuntu:~#
globus@ubuntu:~$ grid-ca-sign -in /etc/grid-security/hostcert_request.pem -out hostsigned.pem
To sign the request
please enter the password for the CA key:
The new signed certificate is at: /home/globus/.globus/simpleCA//newcerts/01.pem
globus@ubuntu:~$
root@ubuntu:~# cp ~globus/hostsigned.pem /etc/grid-security/hostcert.pem
root@ubuntu:~# cd /etc/grid-security/
root@ubuntu:/etc/grid-security# cp hostcert.pem containercert.pem
root@ubuntu:/etc/grid-security# cp hostkey.pem containerket.pem
root@ubuntu:/etc/grid-security# chown globus:globus container*.pem
root@ubuntu:/etc/grid-security# ls -l *.pem
-rw-r--r-- 1 globus globus 2625 2012-07-29 15:44 containercert.pem
-r-------- 1 globus globus 891 2012-07-29 15:44 containerket.pem
-rw-r--r-- 1 root root 2625 2012-07-29 15:42 hostcert.pem
-rw-r--r-- 1 root root 1347 2012-07-29 15:39 hostcert_request.pem
-r-------- 1 root root 891 2012-07-29 15:39 hostkey.pem
root@ubuntu:/etc/grid-security#
Получение сертификата пользователя
univa@ubuntu:~$ source /usr/local/globus-4.0.8/etc/globus-user-env.sh
univa@ubuntu:~$ grid-cert-request
Enter your name, e.g., John Smith: univa
A certificate request and private key is being created.
You will be asked to enter a PEM pass phrase.
This pass phrase is akin to your account password,
and is used to protect your key file.
If you forget your pass phrase, you will need to
obtain a new certificate.
Generating a 1024 bit RSA private key
.....................................................................................++++++.............++++++
writing new private key to '/home/univa/.globus/userkey.pem'
Enter PEM pass phrase:
Verifying - Enter PEM pass phrase:
-----
You are about to be asked to enter information that will be incorporated
into your certificate request.
What you are about to enter is what is called a Distinguished Name or a DN.
There are quite a few fields but you can leave some blank
For some fields there will be a default value,
If you enter '.', the field will be left blank.
-----
Level 0 Organization [Grid]:Level 0 Organizational Unit [GlobusTest]:Level 1 Organizational Unit [simpleCA-ubuntu]:Level 2 Organizational Unit []:Name (e.g., John M. Smith) []:
A private key and a certificate request has been generated with the subject:
/O=Grid/OU=GlobusTest/OU=simpleCA-ubuntu/CN=univa
If the CN=univa is not appropriate, rerun this
script with the -force -cn "Common Name" options.
Your private key is stored in /home/univa/.globus/userkey.pem
Your request is stored in /home/univa/.globus/usercert_request.pem
Please e-mail the request to the Globus Simple CA univa@ubuntu
You may use a command similar to the following:
cat /home/univa/.globus/usercert_request.pem | mail univa@ubuntu
Only use the above if this machine can send AND receive e-mail. if not, please
mail using some other method.
Your certificate will be mailed to you within two working days.
If you receive no response, contact Globus Simple CA at univa@ubuntu
univa@ubuntu:~$ grid-proxy-init -verify -debug
User Cert File: /home/univa/.globus/usercert.pem
User Key File: /home/univa/.globus/userkey.pem
Trusted CA Cert Dir: /etc/grid-security/certificates
Output File: /tmp/x509up_u1000
Your identity: /O=Grid/OU=GlobusTest/OU=simpleCA-ubuntu/CN=univa
Enter GRID pass phrase for this identity:
Creating proxy ........++++++++++++
..................++++++++++++
Done
Proxy Verify OK
Your proxy is valid until: Mon Jul 30 12:42:14 2012
univa@ubuntu:~$ rft -h ubuntu -f /tmp/rft.xfr
Number of transfers in this request: 1
Subscribed for overall status
Termination time to set: 60 minutes
Overall status of transfer:
Finished/Active/Failed/Retrying/Pending
0/1/0/0/0
Overall status of transfer:
Finished/Active/Failed/Retrying/Pending
1/0/0/0/0
All Transfers are completed
univa@ubuntu:~$ diff /etc/group /tmp/rftTest_Done.tmp
univa@ubuntu:~$ globusrun-ws -submit -c /bin/true
Submitting job...Done.
Job ID: uuid:e9708dee-d9df-11e1-81f0-d00d53770a02
Termination time: 07/31/2012 00:45 GMT
Current job state: Active
Current job state: CleanUp
Current job state: Done
Destroying job...Done.
univa@ubuntu:~$
univa@ubuntu:~$ echo $?
0
univa@ubuntu:~$ globusrun-ws -submit -c /bin/false
Submitting job...Done.
Job ID: uuid:0c7abf08-d9e0-11e1-82bc-d00d53770a02
Termination time: 07/31/2012 00:46 GMT
Current job state: Active
Current job state: CleanUp
Current job state: Done
Destroying job...Done.
univa@ubuntu:~$ echo $?
1
univa@ubuntu:~$
