Joaquina - Páginas nuevas [es]

Página principal

2013-09-27T14:38:50Z

127.0.0.1: Página creada con «<big>'''Joaquina: una solución de almacenamiento centralizado de datos'''</big> Joaquina es un proyecto de tesis universitaria la cual tiene como fin el desarrollo y la p...»

<big>'''Joaquina: una solución de almacenamiento centralizado de datos'''</big>

Joaquina es un proyecto de tesis universitaria la cual tiene como fin el desarrollo y la puesta en funcionamiento de una solución de almacenamiento centralizado de datos de alta disponibilidad.

La misma será implementada y puesta en funcionamiento dentro de la Prosecretaría de Informática de la Universidad Nacional de Córdoba.

----

<big>'''Objetivos de esta wiki'''</big>

Esta wiki tiene como objetivo principal almacenar instructivos, articulos y documentos que sirvan para el desarrollo del proyecto.
Actualmente el proyecto Joaquina se encuentra en etapa de desarrollo.

----

<big>'''Instructivos'''</big>

'''A'''
*[[Asignar direccion IP estática en Opensolaris]]
'''I'''
*[[Instalar las Man Pages en Solaris 10]]
*[[Instalar Opensolaris 2009.06 con una HP Smart Array Controller]]
*[[iSCSI Target en Solaris 10]]
'''S'''
*Solaris System Administration Guide: Basic Administration [[http://docs.sun.com/app/docs/doc/817-1985]]
'''X'''
*[[XEN + iSCSI = Live Migration]]
'''Z'''
*[[ZFS: getting started]]
*[[ZFS: root mirror]]

----

<big>'''Links de interés'''</big>

*X4500 + Solaris ZFS + iSCSI [[http://blogs.sun.com/constantin/entry/x4500_solaris_zfs_iscsi_perfect]]
*Listado de papers que hablan sobre distintos sistemas de archivo [[http://www.forensics.nl/filesystems]]
*Como trabaja ZFS [[http://kerneltrap.org/FreeBSD/BSDCan_2008_ZFS_Internals]]
*Drivers del HP Proliant DL585 G2 [[http://h20000.www2.hp.com/bizsupport/TechSupport/DriverDownload.jsp?prodNameId=3288124&lang=en&cc=us&taskId=135&prodClassId=-1&prodTypeId=15351&prodSeriesId=3219717]]
*Especificaciones del HP Proliant DL585 G2 Server [[http://h20000.www2.hp.com/bizsupport/TechSupport/Document.jsp?lang=en&cc=us&objectID=c00908360&prodTypeId=12169&prodSeriesId=3355757]]
*Benchmark con Bonnie++ [[http://linux.com/archive/feature/139742]]

ISCSI Target en Solaris 10

2009-06-20T22:48:49Z

Admin:

El comando '''iscsitadm''' en Solaris permite crear, modificar, borrar, y mostrar estadisticas de la implementación de la RFC 3720 en el sistema.
== Opciones del comando ==
iscsitadm
create
target
initiator
tpgt
modify
target
initiator
tpgt
admin
delete
target
initiator
tpgt
list
target
initiator
tpgt
show
admin
stats

== Creación de dispositivo iSCSI ==
En esta sección se ven ejemplos, para mas detalles recurrir a las referencias. Un target iSCSI puede ser creado de dos maneras:

1.- Comando iscsitadm
# Debido a que no se asigna ningún dispositivo físico (disco o tape) ni lógico (zfs) para la creación del dispositivo iSCSI.
# Se debe declarar lo que se denomina backing store, que es el lugar donde se almacenarán los datos guardados por quienes den uso a este dispositivo exportado.
target:~# iscsitadm modify admin -d /export/sandbox

# Se crea el dispositivo, se limita el tamaño a 2g y se le da un nombre lógico "sandbox"
target:~# iscsitadm create target --size 2g sandbox
2.- Comando zfs
# Se crea un sistema de archivo zfs limitado a 2g que almacenará los datos guardados por quienes den uso a este dispositivo.
target:~# zfs create -V 2g tank/volumes/v2

# Se comparte el dispositivo por iSCSI
target:~# zfs set shareiscsi=on tank/volumes/v2

== Acceso a los dispositivos mediante Autenticación ==
La autenticación para poder acceder a un target puede ser de dos formas: Unidireccional o Bidireccional.

''Unidireccional:'' El iniciador debe proveer un nombre de usuario y contraseña cada vez que quiera acceder a un target. El servidor iSCSI recibirá estos datos y lo comparará con su base de acceso.

''Bidireccional:'' El iniciador y target deben proveerse mutuamente un nombre de usuario y contraseña cada vez que inicie una interacción entre ambos. El iniciador y target (que es el servidor iSCSI) recibirán estos datos y lo compararán con su base de acceso.

La forma mas tradicional de autenticación es la Unidireccional, por lo que será la que se desarrolla a continuación.
Para poder implementar autenticación, es necesario realizar modificaciones tanto en el Servidor iSCSI (que contiene los target) como en los clientes iSCSI (que son los iniciadores). Se va a empezar por el target:

<big>'''Target'''</big>

El servidor iSCSI se encuentra bajo Solaris 10
# Se asigna un nombre de usuario al target. Normalmente es el mismo nombre del servidor
# (en realidad no es necesario si no se usa autenticación bidireccional)
target:~# iscsitadm modify admin -H carola

# Se relaciona un password con el nombre de usuario.
# (en realidad no es necesario si no se usa autenticación bidireccional)
target:~# iscsitadm modify admin -C

# Se asocia el nombre del iniciador (iqn-xxx.xxxx.xxxx) a uno mas sencillo (venus) para poder administrarlo mas facilmente.
target:~# iscsitadm create initiator -n iqn.2005-03.org.open-iscsi:7a9f5ad2d1fa venus

# Se crea un nombre de usuario para el iniciador. En este caso se pone el mismo que el nombre amistoso del punto de anterior.
target:~# iscsitadm modify initiator -H venus venus

# Se relaciona un password con el nombre de usuario.
target:~# iscsitadm modify initiator -C venus

# Finalmente se asocia el iniciador con uno o mas targets creados en la sección Creación de dispositivo iSCSI
target:~# iscsitadm modify target -l venus sandbox

<big>'''Iniciador'''</big>

Depende del cliente iSCSI. A continuación se explica como hacerlo en openSUSE Linux

== Referencias ==
*System Administration Guide: Devices and File Systems - Chapter 14 Configuring Solaris iSCSI Targets and Initiators (Tasks) [[http://docs.sun.com/app/docs/doc/819-2723/fmvcd?q=iSCSI&a=view]]
*Using a ZFS Volume as a Solaris iSCSI Target [[http://docs.sun.com/app/docs/doc/817-2271/gechv?a=view]]
*Man de iscsitadm

Instalar Opensolaris 2009.06 con una HP Smart Array Controller

2009-06-02T15:59:54Z

Admin:

== Installing OpenSolaris 2008.11 on a server with a HP Smart Array Controller ==

I'm quite new to OpenSolaris; insofar as it's like Linux, I'm pretty comfortable, but there appear to be enough little gotchas to make the learning curve a little steeper than one might like.

Take, for instance, the fact that OpenSolaris doesn't ship with the drivers for the almost-ubiquitous HP Smart Array controller. That makes for an installation hiccup that a quick Google search shows many people have found difficult. It's too bad, too: it appears that this has stymied a lot of folks in trying to install the OS.

Like most things, the solution is easy, once you know how to do it

=Boot to the Install CD=

The first task is to boot to the OpenSolaris Live CD, which is also the install CD.
If you haven't downloaded it, yet, you can get it at http://opensolaris.org

=Get the HP Smart Array Driver=

Download the CPQary3 driver, which includes Solaris drivers for most of the recent (and not so recent) Smart Array controllers. As of this writing, the latest version of these drivers is v2.0.0. They can be found here[[http://h20000.www2.hp.com/bizsupport/TechSupport/SoftwareDescription.jsp?lang=en&cc=US&swItem=MTX-30012bd09e11426b9b289142e4]]. The /tmp filesystem has a lot of space on the live CD, so it's probably best to save the file there.
Edit: I see the location of the driver had changed, so I've updated the link above. I also saved off the drivers here, if that's helpful. As always, it' a better idea to go to the source (HP in this case) for files than a second-hand location, but if you can't locate it at their site, it'll remain available here.

=Install the Driver=

Now that we've got the drivers, we'll unpack them and go about installing them:

jack@opensolaris:/tmp$ tar -zxf *.gz
ls
jack@opensolaris:/tmp$ ls
CPQary3-2.0.0-solaris10-i386 dbus-D43WuQsGnK iconf_entries.363
CPQary3-2.0.0-solaris10-i386.tar.gz dbus-EmWPHCv5Ec ogl_select471

Just for simplicity's sake, I renamed the directory, so that it was a bit less unwieldy.

jack@opensolaris:/tmp$ mv CPQary3-2.0.0-solaris10-i386 cpqary
jack@opensolaris:/tmp$ cd cpqary
jack@opensolaris:/tmp/cpqary$ ls
CPQary3.144 CPQary3.pkg LICENSE.CPQary3 RELEASENOTES.CPQary3
CPQary3.iso DU README.CPQary3 tools

Note that the OpenSolaris Live CD logs in with the username 'Jack,' which doesn't have much in the way of priviledges. Instead of sudo, use the pfexec script to run the commands with elevated priviledges.

Now here is where some persistent Googling paid off. There's a bug report at the OpenSolaris site (bug #5860)[[http://defect.opensolaris.org/bz/show_bug.cgi?id=5860]] where a developer suggests a step that makes things all OK:

So here are the rest of the steps:
Create a file on the root filesystem:
jack@opensolaris:/tmp/cpqary$ pfexec touch /ADD_DRV_IGNORE_ROOT_BASEDIR

Once we've done that, we can install the driver we downloaded:
jack@opensolaris:/tmp/cpqary$ pfexec pkgadd -d ./CPQary3.pkg

The following packages are available:
1 CPQary3 HP Smart Array Controller Driver
(i386) 2.0.0,Rev=2008.12.05.01.09

Select package(s) you wish to process (or 'all' to process
all packages). (default: all) [?,??,q]:

Processing package instance from

HP Smart Array Controller Driver(i386) 2.0.0,Rev=2008.12.05.01.09
Copyright 2008 Hewlett-Packard Development Company, L.P.
## Executing checkinstall script.
Using as the package base directory.
## Processing package information.
## Processing system information.
11 package pathnames are already properly installed.
## Verifying package dependencies.
## Verifying disk space requirements.
WARNING:
The /usr filesystem has 0 free blocks. The current installation requires 158 blocks, which includes a required 150 block buffer for open deleted files. 158 more blocks are needed.
WARNING:
The /usr filesystem has 0 free file nodes. The current installation requires 26 file nodes, which includes a required 25 file node buffer for temporary files. 26 more file nodes are needed.

Do you want to continue with the installation of [y,n,?] y
## Checking for conflicts with packages already installed.
## Checking for setuid/setgid programs.

This package contains scripts which will be executed with super-user
permission during the process of installing this package.

Do you want to continue with the installation of [y,n,?] y

Installing HP Smart Array Controller Driver as

## Installing part 1 of 1.
/kernel/drv/amd64/cpqary3
/kernel/drv/cpqary3
/kernel/drv/cpqary3.conf
/usr/share/man/man7d/cpqary3.7d
ERROR: attribute verification of failed
pathname does not exist
[ verifying class ]
ERROR: attribute verification of failed
pathname does not exist
[ verifying class ]
[ verifying class ]
## Executing postinstall script.
Installation of partially failed.

Note a couple of things: the defaults are sufficient, and there are errors in the install.

Happily, the errors are in copying the man pages, which we'll not need, at least for now (the /usr filesystem is read-only in the live CD). The good news is that the driver now is installed for the Smart Array controller.

=Install OpenSolaris=

Double-click on the "install OpenSolaris" icon, and you now should be able to see your drives for installation.

XEN + iSCSI = Live Migration

2009-04-03T18:24:00Z

Admin: Created page with 'Sean dos servidores XEN: larry (172.16.16.2) y moe (172.16.16.1) y un servidor iSCSI llamado carola (172.16.16.4). Crear y levantar en larry un dominio virtual llamado os11.1-hd...'

Sean dos servidores XEN: larry (172.16.16.2) y moe (172.16.16.1) y un servidor iSCSI llamado carola (172.16.16.4).

Crear y levantar en larry un dominio virtual llamado os11.1-hd8 con el siguiente archivo de configuración:

name="os11.1-hd8"
uuid="69fe453d-9e55-26fc-a0db-e7fa3b687384"
memory=384
maxmem=384
vcpus=1
on_poweroff="destroy"
on_reboot="restart"
on_crash="destroy"
localtime=0
keymap="es"
builder="linux"
bootloader="/usr/lib/xen/boot/domUloader.py"
bootargs="--entry=xvda2:/boot/vmlinuz-xen,/boot/initrd-xen"
extra="xencons=tty "
disk=[ 'phy:/dev/iscsi,xvda,w', 'phy:/dev/dvd,xvdb:cdrom,r', ]
vif=[ 'mac=00:16:3e:16:6e:c5', ]
nographic=1

donde /dev/iscsi es un dispositivo de bloques accedido via iSCSI que se encuentra en carola. Este dispositivo cuenta con una tabla de particiones y un OpenSuse 11.1 instalado.

Se deberán seguir los siguientes pasos para lograr una live migration del dominio virtual entre larry y moe

1.- carola deberá compartir el dispositivo de bloques objetivo tanto a larry como a moe

2.- moe debera importar el dispositivo de bloques exportado por carola. Esto puede ser hecho mediante el Iniciador de iSCSI de yast para OpenSuse 11.0.

3.- En moe y larry se debera editar el archivo de configuración de XEN para poder activar la live migration. El archivo de configuración es: /etc/xen/xend-config.sxp

#(xend-unix-server yes)
(xend-relocation-server yes)
(xend-relocation-port 8002)
(xend-relocation-address '')
(xend-relocation-hosts-allow '')
#(xend-relocation-hosts-allow '^localhost$ ^localhost\\.localdomain$')

4.- Reiniciar el servicio xend (rcxend)

5.- Abrir el puerto TCP 8002 tanto en larry como en moe.

6.- Ejecutar la live migration

xm migrate --live os11.1-hd8 172.16.16.1

7.- Abrir consolas en larry y moe y observar la evolución de la live migration

watch -n1 xm list

ZFS: root mirror

2009-03-22T23:17:32Z

Admin: Created page with 'This is a simple Tutorial how you can create a bootable ZFS Root Mirror with Opensolaris. I had some help from both Opensolaris-Forums (com/org) and this Blog from Malachi. And ...'

This is a simple Tutorial how you can create a bootable ZFS Root Mirror with Opensolaris. I had some help from both Opensolaris-Forums (com/org) and this Blog from Malachi.

And here we go with the Tutorial:

Making a bootable ZFS Root Mirror

1. Install Opensolaris to Disk A (c3d0s0).

2. Format Disk B (c3d1s0) properly:
host:# format
(choose fdisk)
(create 100% Standard Solaris Partition over the full Disk)

3. Overwrite the Diskformat properly:
host:# prtvtoc /dev/rdsk/c3d0s2 | fmthard -s - /dev/rdsk/c3d1s2
(NOTE: s2! on BOTH Disks)

4. Attach Disk B to the ZFS Root Pool:
host:# zpool attach -f rpool c3d0s0 c3d1s0

5. Install the GRUB-Stuff to Disk B:
host:# installgrub -m /boot/grub/stage1 /boot/grub/stage2 /dev/rdsk/c3d1s0

6. Test the worst Case: Disk A fails, you can still boot into Disk B

*Remove Disk A
*Replace it with an emtpy Disk C
*Start the System: Choose to boot from Disk B in the Bios
*Repeat Steps 2. till 5. for Disk C (swap c3d0s0 and c3d1s0)
*Start the System like before (from Disk C)

Fuente: http://darkstar-solaris.blogspot.com/2008/09/zfs-root-mirror.html

Instalar las Man Pages en Solaris 10

2009-03-22T21:05:31Z

Admin: Created page with 'Para la instalacion de los manuales en Solaris 10 son necesarios dos paquetes: *SUNWman *SUNWdoc El SUNWman es el paquete que contiene los binarios del comando man y el paquete...'

Para la instalacion de los manuales en Solaris 10 son necesarios dos paquetes:

*SUNWman
*SUNWdoc

El SUNWman es el paquete que contiene los binarios del comando man y el paquete SUNWdoc es el que contiene la informacion sobre los comandos.

Una explicacion desde cero de como instalar estos dos paquetes:

1. Se crea el punto de montaje (cuando se instala Solaris con algunos grupos de software este directorio se crea automaticamente; cuando se instala el CORE no)

#mkdir /cdrom

2. Se monta el cd o dvd que contenga los paquetes

#mount -F hsfs /dev/dsk/c1t0d0s0 /cdrom

3.se instala el paquete SUNWman

#pkgadd -d /cdrom/Solaris_10/Product/ SUNWman

4.Se instala el paquete SUNWdoc

#pkgadd -d /cdrom/Solaris_10/Product/ SUNWdoc

y ya queda, claro que el ejm que expongo es para un caso con un cd o dvd, hay otras formas de instalar los paquetes, pero eso es otro tema.

Casos de uso

2009-03-17T18:54:22Z

Admin: Created page with '*Casos de uso: Un metodo practico explorar Requerimientos http://joaquina.unc.edu.ar/documentacion/bibliografia/CasosDeUso.pdf'

*Casos de uso: Un metodo practico explorar Requerimientos [[http://joaquina.unc.edu.ar/documentacion/bibliografia/CasosDeUso.pdf]]

ZFS: getting started

2009-03-17T17:49:37Z

Admin:

==Getting Started with ZFS==

Everything you hate about managing file systems and volumes is gone: you don't have to format, newfs, mount, edit /etc/vfstab, fsck, growfs, metadb, metainit, etc.

Meet your new best friends: zpool(1M) and zfs(1M).

ZFS is easy, so let's get on with it! It's time to create your first pool:

# zpool create tank c1t2d0

You now have a single-disk storage pool named tank, with a single file system mounted at /tank. There is nothing else to do.

If you want mirrored storage for mail and home directories, that's easy too:

Create the pool:

# zpool create tank mirror c1t2d0 c2t2d0

Create the /var/mail file system:

# zfs create tank/mail

# zfs set mountpoint=/var/mail tank/mail

Create home directories, and mount them all in /export/home/<username>:

# zfs create tank/home

# zfs set mountpoint=/export/home tank/home

# zfs create tank/home/ahrens

# zfs create tank/home/billm

# zfs create tank/home/bonwick

# zfs create tank/home/eschrock

ZFS file systems are hierarchical: each one inherits properties from above. In this example, the mountpoint property is inherited as a pathname prefix. That is, tank/home/ahrens is automatically mounted at /export/home/ahrens because tank/home is mounted at /export/home. You don't have to specify the mountpoint for each individual user — you just tell ZFS the pattern.

This is how we actually set up home directory and mail service on zion.eng, which has been running ZFS for over a year and a half.

But wait, there's more!

ZFS provides built-in compression. To compress all home directories:

# zfs set compression=on tank/home

To give ahrens a 10G quota:

# zfs set quota=10g tank/home/ahrens

To give bonwick a 100G reservation (membership has its privileges):

# zfs set reservation=100g tank/home/bonwick

To automatically NFS-export all home directories read/write:

# zfs set sharenfs=rw tank/home

To scrub all disks and verify the integrity of all data in the pool:

# zpool scrub tank

To replace a flaky disk:

# zpool replace tank c2t2d0 c4t1d0

To add more space:

# zpool add tank mirror c5t1d0 c6t1d0

To move your pool from SPARC machine 'sparky' to AMD machine 'amdy':

[on sparky]
# zpool export tank

Physically move your disks from sparky to amdy.

[on amdy]
# zpool import tank

Everything will just work — ZFS has 'adaptive endianness' to cope with different byte order on different platforms.

You get the idea: it's simple. Any common ZFS operation can be done with a single short command.

Asignar direccion IP estática en Opensolaris

2009-03-17T03:17:46Z

Admin:

En este instructivo se explica rápidamente la configuración estática de red en Opensolaris.
La misma fue probada y funcionó correctamente en un Opensolaris 2008.11 y en Solaris 10

==Beyond DHCP with DNS and Routing in OpenSolaris==

I've finally had time to install OpenSolaris on bare metal. Previously I've installed it under VirtualBox on my Mac and Linux machines. The networking configuration really had me pulling out my hair. If you knew me, you'd know I don't have much hair so this means I was really desperate. Here's some helpful pointers to get started with networking beyond the default DHCP settings for DNS hostname resolution and routing.

==Background==

First, I should provide some background. My office (home office) networking scheme includes a cable modem, 3 non-commercial routers (networks), and a switch. I'm running "Bind" on a Kubuntu machine as my DNS server. I know, I'll convert all this over to OpenSolaris when I learn more about it. So each machine on my networks has an assigned IP address and hostname mapped by the DNS server. Naturally, when I run my OpenSolaris machine, I want it to have a static IP address and a hostname. In the future I'm going to look into MultiCast DNS. But for now, I just wanted to add my new OpenSolaris machine to my network.

==Changing From a DHCP assigned IP Address to a Static IP Address ==

The first step is to configure NWAM (Network Auto-Magic) so my wired ethernet interface is used instead of my wireless interface. I also need to tell it to use a static IP address for the wired interface. To do this, I edited the NWAM config file "llP" like this:

pfexec vi /etc/nwam/llp

I changed it to look like this:

e1000g0 static 192.168.1.17

ath0 dhcp

Notice that the wired interface is before the wireless interface. This is how NWAM determines which interface to use first. Note - the nwamd man page states, "Note, however, that this interface is Volatile and may change in a future release."

Since I changed NWAM, I have to restart nwamd (the NWAM daemon).

pfexec svcadm restart nwam

--------------------------
'''Comentario extra (de Ary):'''

Otra forma de cambiar de DHCP a IP estática es deshabilitar el servicio nwam (configuración automática de red) y habilitar el default:

svcadm disable svc:/network/physical:nwam

svcadm enable svc:/network/physical:default

luego se crea un archivo llamado /etc/hostname.[driver_de_placa_de_red] y dentro de ese archivo se coloca una sola linea con dirección IP y máscara de red

En mi caso:

#echo 10.0.0.6/24 > /etc/hostname.rge0

'''Fin comentario (de Ary)'''
--------------------------

==Getting DNS to Work Correctly==

Since I went to all that work when I setup Bind (DNS), I really wanted to use it. My DNS server does forwarding so if the hostname lookup fails, the request is forwarded to "real" DNS servers somewhere in the ether to get IP addresses for hostnames like "yahoo.com" and "davidbotterill.com" (couldn't resist the plug :) ).

OpenSolaris by default uses NIS (Network Information Service) AKA YellowPages. So I had to tell NIS to use DNS for hostname resolution. This is a fairly simple task. I simply had to copy the provided nsswitch file like this.

pfexec cp /etc/nsswitch.dns /etc/nsswitch.conf

The DNS client is already running. I know this because I ran this command.

svcs -a | grep dns

and saw this result

online 14:17:45 svc:/network/dns/client:default

If you remember from networking 101, the DNS client uses "/etc/resolv.conf" to find the "nameserver". So I ran

pfexec vi /etc/resolv.conf

made sure I had this entry in there.

nameserver 192.168.1.2

==Routing==

So now I had a static IP. Doing "dig yahoo.com" returned valid IP addresses. But, I could still not "ping yahoo.com". You guessed it. There was a routing problem. I dug around in some of the service configuration files, particularly "/lib/svc/method/net-routing-setup" and found that without DHCP, OpenSolaris routing checks for this static route file.

/etc/defaultrouter

Apparently, if I had real routers that supported RIP (Routing Information Protocol), OpenSolaris would discover the route out to the internet automatically. But remember, I'm running home routers not Cisco routers. :) I think some of them support RIP but I'll save that for another day.

In the "/etc/defaultrouter" file I put the IP address of my gateway (the router IP address) for the network my OpenSolaris machine is on. In my case this is "192.168.1.1". Now I need to restart the routing by running the following command.

pfexec svcadm restart network/routing-setup

Fuente: [[http://blogs.sun.com/observatory/entry/beyond_dhcp_with_dns_and]]

'''Autor: Ary'''