Difference: InstallingAndConfiguringNova (1 vs. 25)

Revision 252012-10-22 - EnricoFattibene

Line: 1 to 1
Changed:
<
<
META TOPICPARENT name="GestioneOpenstack"
>
>
META TOPICPARENT name="GestioneServiziGenerali.GestioneOpenstack"
 

Installazione e configurazione del servizio Compute (Nova)

Line: 55 to 55
 # chkconfig libvirtd on

# /etc/init.d/libvirtd restart

Changed:
<
<

Servizi nova

>
>

Servizio nova

 
  • Modificare due file in /etc/nova nel seguente modo.
    • Contentuto completo di nova.conf :

Line: 198 to 198
 
Changed:
<
<

Gruppi di sicurezza: abilitazione di SSH e ICMP

>
>

Gruppi di sicurezza: abilitazione di SSH e ICMP

 Il servizio Compute usa i concetti di gruppi di sicurezza per controllare che i protocolli di rete (TCP, UDP, ICMP), le porte e gli indirizzi IP permettano di accedere alle istanze.

  • Per mostrare la lista dei gruppi di sicurezza usare il seguente comando:
Line: 232 to 232
 


Changed:
<
<

Installare e impostare l'avvio automatico dei servizi legati a ISCSI

>
>

Installare e impostare l'avvio automatico dei servizi legati a ISCSI

 
  • Per poter fare l'attach di un volume nova ad l'instanza di una macchina virtuale necessario installare ed avviare il servizio iscsi-initiator-utils su ogni Compute Node. Controllare quindi che sia installato attraverso il seguente comando:
    yum install iscsi-initiator-utils
Line: 246 to 246
 

-- PaoloVeronesi - 2012-08-30 \ No newline at end of file

Added:
>
>
META TOPICMOVED by="EnricoFattibene" date="1350916398" from="GestioneServiziGenerali.InstallingAndConfiguringNova" to="MarcheCloud.InstallingAndConfiguringNova"

Revision 242012-10-18 - MatteoManzali

Line: 1 to 1
 
META TOPICPARENT name="GestioneOpenstack"

Installazione e configurazione del servizio Compute (Nova)

Line: 241 to 241
 
service iscsid force-start
Changed:
<
<
  • Per settare l'avvio automatico:
    • Creare uno script /etc/rc.d/init.d/force-iscsid che possa far partire il servizio iscsid in maniera forzata:
      #!/bin/bash
      
      # Source function library.
      . /etc/rc.d/init.d/functions
      
      case "$1" in
      start)
      service iscsid force-start
      ;;
      stop)
      service iscsid stop
      ;;
      restart)
      service iscsid stop
      service iscsid force-start
      ;;
      status)
      service iscsid status
      ;;
      *)
      echo "Usage: force-iscsid {start|stop|restart|status}"
      exit 1
      esac
      exit 0
      
    • Cambiare i diritti al file:
      chmod 755 /etc/rc.d/init.d/force-iscsid
      
    • Settare il default SELinux file context per lo script appena creato:
      # restorecon -R -v /etc/rc.d/init.d/force-iscsid
      
>
>
  • Nota bene: non possibile usare il comando chkconfig per far partire il servizio iscsid in automatico all'avvio del server, quindi necessario farlo partire manualmente ad ogni riavvio, utilizzando il comando service iscsid force-start .
 

Revision 232012-10-18 - PaoloVeronesi

Line: 1 to 1
 
META TOPICPARENT name="GestioneOpenstack"

Installazione e configurazione del servizio Compute (Nova)

Line: 37 to 37
 

Configurazione del servizio Compute

Added:
>
>

Servizio libvirtd

  • Editare il file /etc/libvirt/libvirtd.conf e assicurarsi siano impostati i seguenti valori:
# OPENSTACK LIVE MIGRATION
listen_tls = 0
listen_tcp = 1
auth_tcp = "none"

  • Editare il file /etc/sysconfig/libvirtd e assicurarsi che ci siano le impostazioni come seguono:
LIBVIRTD_ARGS="--listen"

  • Far partire libvirtd:
# chkconfig libvirtd on

# /etc/init.d/libvirtd restart

Servizi nova

 
  • Modificare due file in /etc/nova nel seguente modo.
    • Contentuto completo di nova.conf :

Line: 178 to 197
 


Deleted:
<
<

Configurazione degli indirizzi IP Floating pubblici

Indirizzi IP pubblici e privati

  • Ad ogni istanza virtuale viene automaticamente assegnato un IP privato (appartenente alla sottorete creata al punto precedente). E' possibile assegnare indirizzi pubblici alle istanze. In tal caso verificare la presenza della seguente riga nel file nova.conf :
    public_interface = eth0
    
    Far ripartire il servizio nova-network dopo aver cambiato il nova.conf .
 
Deleted:
<
<

Abilitazione di IP forwarding

  • Di default l'IP forwarding disabilitato sulla maggior parte delle distribuzioni Linux. Per poter assegnare indirizzi pubblici alle macchine necessario che l'IP forwarding sia abilitato. Verificare se abilitato tramite il seguente comando:
    # sysctl net.ipv4.ip_forward
    net.ipv4.ip_forward = 0
    
    In questo esempio disabilitato. e' possibile abilitarlo al volo usando il seguente comando:
    # sysctl -w net.ipv4.ip_forward=1
    
    Al fine di rendere permanente questa modifica, editare il file /etc/sysctl.conf inserendo o modificando la seguente riga:
    net.ipv4.ip_forward = 1
    

Creazione di una lista di IP Floating pubblici disponibili

  • Nova pu gestire una lista di IP pubblici che possano essere assegnati alle istanze virtuali. Per aggiungere un IP alla lista:
    # nova-manage floating create <AVAILABLE_PUBLIC_IP>
    
    Dove <AVAILABLE_PUBLIC_IP> un IP disponibile. E' possibile aggiungere una sottorete tramite:
    # nova-manage floating create --ip_range=<SUBNET>
    
    Dove <SUBNET> una sottorete disponibile (es. 131.154.100.0/24). Per la gestione della lista di IP pubblici sono disponibili i seguenti comandi:
    • nova-manage floating list : mostra la lista degli IP pubblici inseriti
    • nova-manage floating create : aggiunge un IP alla lista
    • nova-manage floating create --ip-range= : aggiunge una sottorete alla lista
    • nova-manage floating delete : rimuove un IP dalla lista
    • nova-manage floating delete --ip-range= : rimuove una sottorete dalla lista


 

Gruppi di sicurezza: abilitazione di SSH e ICMP

Il servizio Compute usa i concetti di gruppi di sicurezza per controllare che i protocolli di rete (TCP, UDP, ICMP), le porte e gli indirizzi IP permettano di accedere alle istanze.

Revision 222012-10-17 - MatteoManzali

Line: 1 to 1
 
META TOPICPARENT name="GestioneOpenstack"

Installazione e configurazione del servizio Compute (Nova)

Line: 263 to 263
 
service iscsid force-start
Changed:
<
<
  • Settare l'avvio automatico:
>
>
  • Per settare l'avvio automatico:
    • Creare uno script /etc/rc.d/init.d/force-iscsid che possa far partire il servizio iscsid in maniera forzata:
 
Changed:
<
<
xxx
>
>
#!/bin/bash

# Source function library. . /etc/rc.d/init.d/functions

case "$1" in start) service iscsid force-start ;; stop) service iscsid stop ;; restart) service iscsid stop service iscsid force-start ;; status) service iscsid status ;; *) echo "Usage: force-iscsid {start|stop|restart|status}" exit 1 esac exit 0

    • Cambiare i diritti al file:
      chmod 755 /etc/rc.d/init.d/force-iscsid
      
    • Settare il default SELinux file context per lo script appena creato:
      # restorecon -R -v /etc/rc.d/init.d/force-iscsid
 


Revision 212012-10-17 - PaoloVeronesi

Line: 1 to 1
 
META TOPICPARENT name="GestioneOpenstack"

Installazione e configurazione del servizio Compute (Nova)

Line: 91 to 91
 fixed_range = 192.168.122.0/24

# NOVNC CONSOLE

Changed:
<
<
#novncproxy_base_url=http://192.168.206.130:6080/vnc_auto.html

# Change vncserver_proxyclient_address and vncserver_listen to match each compute host vncserver_listen = vncserver_proxyclient_address =

>
>
vnc_enabled = true vncserver_listen = 0.0.0.0 vncserver_proxyclient_address = 131.154.100.111 novncproxy_base_url=http://openstack-01.cnaf.infn.it:6080/vnc_auto.html xvpvncproxy_base_url=http://openstack-01.cnaf.infn.it:6081/console
  # Qpid qpid_hostname = openstack-01.cnaf.infn.it

Revision 202012-10-17 - MatteoManzali

Line: 1 to 1
 
META TOPICPARENT name="GestioneOpenstack"

Installazione e configurazione del servizio Compute (Nova)

Line: 254 to 254
 

Installare e impostare l'avvio automatico dei servizi legati a ISCSI

Changed:
<
<
  • Per poter fare l'attach di un volume nova ad l'instanza di una macchina virtuale necessario installare ed avviare il servizio iscsi-initiator-utils su ogni ComputeNode. Controllare quindi che sia installato attraverso il seguente comando:
>
>
  • Per poter fare l'attach di un volume nova ad l'instanza di una macchina virtuale necessario installare ed avviare il servizio iscsi-initiator-utils su ogni Compute Node. Controllare quindi che sia installato attraverso il seguente comando:
 
yum install iscsi-initiator-utils

Revision 192012-10-17 - PaoloVeronesi

Line: 1 to 1
 
META TOPICPARENT name="GestioneOpenstack"

Installazione e configurazione del servizio Compute (Nova)

Line: 74 to 74
 #s3_host=192.168.206.130

# GLANCE

Changed:
<
<
#image_service=nova.image.glance.GlanceImageService #glance_api_servers=192.168.206.130:9292
>
>
image_service=nova.image.glance.GlanceImageService glance_api_servers=192.168.206.130:9292
  # NETWORK network_manager = nova.network.manager.FlatDHCPManager

Revision 182012-10-17 - MatteoManzali

Line: 1 to 1
 
META TOPICPARENT name="GestioneOpenstack"

Installazione e configurazione del servizio Compute (Nova)

Line: 251 to 251
 
icmp -1 -1 0.0.0.0/0  
+-------------+-----------+---------+-----------+--------------+
Added:
>
>

Installare e impostare l'avvio automatico dei servizi legati a ISCSI

  • Per poter fare l'attach di un volume nova ad l'instanza di una macchina virtuale necessario installare ed avviare il servizio iscsi-initiator-utils su ogni ComputeNode. Controllare quindi che sia installato attraverso il seguente comando:
    yum install iscsi-initiator-utils
    
  • Far partire il servizio:
    service iscsid force-start
    
  • Settare l'avvio automatico:
    xxx
    
 

-- PaoloVeronesi - 2012-08-30 \ No newline at end of file

Revision 172012-10-15 - MatteoManzali

Line: 1 to 1
 
META TOPICPARENT name="GestioneOpenstack"

Installazione e configurazione del servizio Compute (Nova)

Line: 154 to 154
 # nova-manage service list

Binary Host Zone Status State Updated_At

Changed:
<
<
nova-scheduler stack-03.cnaf.infn.it nova enabled smile 2012-08-31 09:46:24 nova-compute stack-03.cnaf.infn.it nova enabled smile 2012-08-31 09:46:26 nova-network stack-03.cnaf.infn.it nova enabled smile 2012-08-31 09:46:25 nova-cert stack-03.cnaf.infn.it nova enabled smile 2012-08-31 09:46:24 nova-volume stack-03.cnaf.infn.it nova enabled smile 2012-08-31 09:46:24
>
>
nova-cert openstack-01.cnaf.infn.it nova enabled smile 2012-10-15 14:46:04 nova-consoleauth openstack-01.cnaf.infn.it nova enabled smile 2012-10-15 14:45:54 nova-console openstack-01.cnaf.infn.it nova enabled smile 2012-10-15 14:46:04 nova-scheduler openstack-01.cnaf.infn.it nova enabled smile 2012-10-15 14:45:55 nova-compute openstack-01.cnaf.infn.it nova enabled smile 2012-10-15 14:45:54 nova-volume openstack-01.cnaf.infn.it nova enabled smile 2012-10-15 14:45:55 nova-network openstack-01.cnaf.infn.it nova enabled smile 2012-10-15 14:46:01 nova-compute openstack-02.cnaf.infn.it nova enabled smile 2012-10-15 14:45:57 nova-network openstack-02.cnaf.infn.it nova enabled smile 2012-10-15 14:46:03 nova-compute openstack-03.cnaf.infn.it nova enabled smile 2012-10-15 14:46:02 nova-network openstack-03.cnaf.infn.it nova enabled smile 2012-10-15 14:46:02
 

  • Creare la sottorete privata, i cui IP verranno assegnati alle istanze delle macchine virtuali, utilizzando l'interfaccia virtuale (nel caso in esempio virbr0). Il seguente comando, ad esempio, crea una sottorete con range 192.168.122.0/24.

Revision 162012-10-12 - EnricoFattibene

Line: 1 to 1
 
META TOPICPARENT name="GestioneOpenstack"
Changed:
<
<

Installazione e configurazione del servizio Compute (NOVA)

>
>

Installazione e configurazione del servizio Compute (Nova)

 

Configurazione dell'Hypervisor (KVM)

Line: 35 to 35
  Nota bene: non viene mostrato nessun output ma modificato il file di configurazione.
Added:
>
>

 

Configurazione del servizio Compute

  • Modificare due file in /etc/nova nel seguente modo.
    • Contentuto completo di nova.conf :
Line: 169 to 170
 1 192.168.122.0/24 None 192.168.122.2 8.8.4.4 None None None 052f9b4b-e6d7-4ad9-a3f1-929e80008372
Changed:
<
<

Configurazione degli indirizzi IP (Floating) pubblici

>
>

Configurazione degli indirizzi IP Floating pubblici

 

Indirizzi IP pubblici e privati

Changed:
<
<
Ad ogni istanza virtuale viene automaticamente assegnato un IP privato (appartenente alla sottorete creata al punto precedente). E' possibile assegnare indirizzi pubblici alle istanze. In tal caso verificare la presenza della seguente riga nel file nova.conf If you plan to use this feature, you must add the following to your nova.conf file to specify which interface the nova-network service will bind public IP addresses to:
>
>
  • Ad ogni istanza virtuale viene automaticamente assegnato un IP privato (appartenente alla sottorete creata al punto precedente). E' possibile assegnare indirizzi pubblici alle istanze. In tal caso verificare la presenza della seguente riga nel file nova.conf :
 
public_interface = eth0
Changed:
<
<
Restart the nova-network service if you change nova.conf while the service is running.
>
>
Far ripartire il servizio nova-network dopo aver cambiato il nova.conf .
 
Changed:
<
<

Enabling IP forwarding

By default, the IP forwarding is disabled on most of Linux distributions. The floating IP feature requires the IP forwarding enabled in order to work, you can check if the forwarding is enabled by running the following command:
>
>

Abilitazione di IP forwarding

  • Di default l'IP forwarding disabilitato sulla maggior parte delle distribuzioni Linux. Per poter assegnare indirizzi pubblici alle macchine necessario che l'IP forwarding sia abilitato. Verificare se abilitato tramite il seguente comando:
 
# sysctl net.ipv4.ip_forward
net.ipv4.ip_forward = 0
Changed:
<
<
In this example, the IP forwarding is disabled. You can enable it on the fly by running the following command:
>
>
In questo esempio disabilitato. e' possibile abilitarlo al volo usando il seguente comando:
 
Changed:
<
<
$ sysctl -w net.ipv4.ip_forward=1
>
>
# sysctl -w net.ipv4.ip_forward=1
 
Changed:
<
<
In order to make the changes permanent, edit the /etc/sysctl.conf and update the IP forwarding setting : /verbatim>
>
>
Al fine di rendere permanente questa modifica, editare il file /etc/sysctl.conf inserendo o modificando la seguente riga:

 net.ipv4.ip_forward = 1
Changed:
<
<

Creating a List of Available Floating IP Addresses

Nova maintains a list of floating IP addresses that are available for assigning to instances. Use the nova-manage floating create command to add entries to this list, as root. For example:

nova-manage floating create 131.154.101.220 The following nova-manage commands apply to floating IPs.

  • nova-manage floating list: List the floating IP addresses in the pool.
  • nova-manage floating create [cidr]: Create specific floating IPs for either a single address or a subnet.
  • nova-manage floating delete [cidr]: Remove floating IP addresses using the same parameters as the create command.

Adding a Floating IP to an Instance

Adding a floating IP to an instance is a two step process:
  1. nova floating-ip-create: Allocate a floating IP address from the list of available addresses.
  2. nova add-floating-ip: Add an allocated floating IP address to a running instance.

Here's an example of how to add a floating IP to a running instance with an ID of 63c5b9ba-3308-43ce-af61-d7b5dbc08c15

>
>

Creazione di una lista di IP Floating pubblici disponibili

  • Nova pu gestire una lista di IP pubblici che possano essere assegnati alle istanze virtuali. Per aggiungere un IP alla lista:
    # nova-manage floating create <AVAILABLE_PUBLIC_IP>
    
    Dove <AVAILABLE_PUBLIC_IP> un IP disponibile. E' possibile aggiungere una sottorete tramite:
 
Changed:
<
<
# nova floating-ip-create +-----------------+-------------+----------+------+
Ip Instance Id Fixed Ip Pool
+-----------------+-------------+----------+------+
131.154.101.220 None None nova
+-----------------+-------------+----------+------+
>
>
# nova-manage floating create --ip_range= Dove <SUBNET> una sottorete disponibile (es. 131.154.100.0/24). Per la gestione della lista di IP pubblici sono disponibili i seguenti comandi:
    • nova-manage floating list : mostra la lista degli IP pubblici inseriti
    • nova-manage floating create : aggiunge un IP alla lista
    • nova-manage floating create --ip-range= : aggiunge una sottorete alla lista
    • nova-manage floating delete : rimuove un IP dalla lista
    • nova-manage floating delete --ip-range= : rimuove una sottorete dalla lista
 
Changed:
<
<
# nova add-floating-ip 63c5b9ba-3308-43ce-af61-d7b5dbc08c15 131.154.101.220
>
>

Gruppi di sicurezza: abilitazione di SSH e ICMP

Il servizio Compute usa i concetti di gruppi di sicurezza per controllare che i protocolli di rete (TCP, UDP, ICMP), le porte e gli indirizzi IP permettano di accedere alle istanze.
 
Changed:
<
<
# nova-manage floating list c10d9c9f296b47f8a1212dd7a98357e0 131.154.101.220 63c5b9ba-3308-43ce-af61-d7b5dbc08c15 nova eth0
>
>
  • Per mostrare la lista dei gruppi di sicurezza usare il seguente comando:
    # nova secgroup-list
    +---------+-------------+
    |   Name  | Description |
    +---------+-------------+
    | default | default     |
    +---------+-------------+
 
Changed:
<
<
If the instance no longer needs a public address, remove the floating IP address from the instance and de-allocate the address:
>
>
  • Abilitare l'accesso sulla porta TCP 22 (SSH) per tutti gli indirizzi di Nova:
 
Changed:
<
<
# nova remove-floating-ip 63c5b9ba-3308-43ce-af61-d7b5dbc08c15 131.154.101.220 # nova floating-ip-delete 131.154.101.220
>
>
# nova secgroup-add-rule default tcp 22 22 0.0.0.0/0 +-------------+-----------+---------+-----------+--------------+
IP Protocol From Port To Port IP Range Source Group
+-------------+-----------+---------+-----------+--------------+
tcp 22 22 0.0.0.0/0  
+-------------+-----------+---------+-----------+--------------+
 
Changed:
<
<

Automatically adding floating IPs

The nova-network service can be configured to automatically allocate and assign a floating IP address to virtual instances when they are launched. Add the following line to nova.conf and restart the nova-network service
>
>
  • Abilitare il traffico ICMP (ping) per tutti gli IP di Nova:
 
Changed:
<
<
auto_assign_floating_ip=True
>
>
# nova secgroup-add-rule default icmp -1 -1 0.0.0.0/0 +-------------+-----------+---------+-----------+--------------+
IP Protocol From Port To Port IP Range Source Group
+-------------+-----------+---------+-----------+--------------+
icmp -1 -1 0.0.0.0/0  
+-------------+-----------+---------+-----------+--------------+
 
Changed:
<
<
Note that if this option is enabled and all of the floating IP addresses have already been allocated, the nova boot command will fail with an error.
>
>

  -- PaoloVeronesi - 2012-08-30

Revision 152012-10-11 - EnricoFattibene

Line: 1 to 1
 
META TOPICPARENT name="GestioneOpenstack"

Installazione e configurazione del servizio Compute (NOVA)

Changed:
<
<

Configurare l'Hypervisor (KVM)

  • Install virtualizzation RPMs
>
>

Configurazione dell'Hypervisor (KVM)

  • Installare i pacchetti per la virtualizzazione:
 
# yum install qemu-kvm qemu-img virt-manager libvirt libvirt-python python-virtinst libvirt-client bridge-utils
# yum groupinstall Virtualization "Virtualization Client" "Virtualization Platform" "Virtualization Tools"
# yum install openstack-utils memcached qpid-cpp-server openstack-nova dnsmasq-utils  python-keystone-auth-token
Changed:
<
<
  • Pre-configured the network (di default viene su cos).
>
>
  • Verificare che sia attiva l'interfaccia di rete virtuale, chiamata di default virbr0. Il comando ifconfig dovrebbe mostrarla nel suo output:
 
Deleted:
<
<
# ifconfig virbr0
 virbr0 Link encap:Ethernet HWaddr 52:54:00:54:65:A1 inet addr:192.168.122.1 Bcast:192.168.122.255 Mask:255.255.255.0 UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
Line: 23 to 22
  RX bytes:0 (0.0 b) TX bytes:7585 (7.4 KiB)
Deleted:
<
<
 
  • Requisiti di configurazione per RHEL
    • Assicurarsi che nel file /etc/qpidd.conf sia settato auth=no .
Changed:
<
<
    • use the openstack-config package to turn off force DHCP releases: sudo openstack-config --set /etc/nova/nova.conf DEFAULT force_dhcp_release False (Non viene mostrato nessun output ma modificato il file di configurazione.)
    • If you intend to use guest images that don't have a single partition, then allow libguestfs to inspect the image so that files can be injected, by setting: sudo openstack-config --set /etc/nova/nova.conf DEFAULT libvirt_inject_partition -1 (Non viene mostrato nessun output ma modificato il file di configurazione.)

Configuring OpenStack Compute

Da modificare due file in /etc/nova:

<--/twistyPlugin twikiMakeVisibleInline-->
>
>
    • Attraverso il comando openstack-config settare a False il parametro force_dhcp_release :
      # openstack-config --set /etc/nova/nova.conf DEFAULT force_dhcp_release False
      
      Nota bene: non viene mostrato nessun output ma modificato il file di configurazione.
    • Se si intende utilizzare immagini che non usano una singola partizione, eseguire il seguente comando:
      # openstack-config --set /etc/nova/nova.conf DEFAULT libvirt_inject_partition -1
      
      Nota bene: non viene mostrato nessun output ma modificato il file di configurazione.
 
Added:
>
>

Configurazione del servizio Compute

  • Modificare due file in /etc/nova nel seguente modo.
    • Contentuto completo di nova.conf :
 
[DEFAULT]
# LOG/STATE
Line: 61 to 58
 iscsi_helper = tgtadm

# DATABASE del Cloud Controller

Changed:
<
<
sql_connection=mysql://nova:XXXXXX@hostname1.domain/nova
>
>
sql_connection = mysql://nova:@openstack-01.cnaf.infn.it/nova
  # COMPUTE libvirt_type = kvm
Line: 100 to 97
 vncserver_proxyclient_address =

# Qpid

Changed:
<
<
qpid_hostname =
>
>
qpid_hostname = openstack-01.cnaf.infn.it
 rpc_backend = nova.rpc.impl_qpid

# OTHER

Line: 114 to 111
 root_helper = sudo nova-rootwrap remove_unused_base_images = True
Changed:
<
<
<--/twistyPlugin-->

  • verificare che in fondo a /etc/nova/api-paste.ini ci siano le seguenti configurazioni (la parte prima non si tocca, 131.154.101.242 l'ip di keystone ).
<--/twistyPlugin twikiMakeVisibleInline-->
>
>
Dove:
      • <VOLUME_NAME> il nome del volume fisico del server che si sta configurando
      • <YOUR_NOVADB_PASSWORD> la password dell'utente "nova" del DB "nova" del Cloud Controller
      • <THIS_SERVER_IP> l'IP del server che si sta configurando
      • nei parametri sql_connection e qpid_hostname "openstack-01.cnaf.infn.it" il server che ospita il Cloud Controller
      • nel parametro flat_network_bridge "virbr0" l'interfaccia di rete virtuale del server che si sta configurando
        
        
    • Parte finale di /etc/nova/api-paste.ini (la parte precedente rimane invariata):
 
[...]
Line: 141 to 135
 admin_user = nova admin_password =
Changed:
<
<
<--/twistyPlugin-->

  • lanciare i seguenti comandi:
>
>
Dove:
      • <KEYSTONE_SERVICE_IP> l'IP del server che ospita Keystone (nel caso del prototipo l'IP di openstack-01.cnaf.infn.it)
      • <NOVA_PASSWORD> la password che stata associata all'utente del servizio Nova in Keystone
        
        
  • Nota bene: il comando nova-manage potrebbe dare in output alcuni messaggi di Warning su metodi deprecati.
    
    
  • Per far partire i servizi di Nova ed inizializzare il DB, lanciare i seguenti comandi:
 
# for svc in api objectstore compute network volume scheduler cert; do echo openstack-nova-$svc; service openstack-nova-$svc stop ; chkconfig openstack-nova-$svc on; done
Deleted:
<
<
 # nova-manage db sync
Deleted:
<
<
 # for svc in api objectstore compute network volume scheduler cert; do echo openstack-nova-$svc; /etc/init.d/openstack-nova-$svc start ; done
Line: 152 to 148
 # for svc in api objectstore compute network volume scheduler cert; do echo openstack-nova-$svc; /etc/init.d/openstack-nova-$svc start ; done
Changed:
<
<
  • Sul Cloud controller, verificare lo stato dei NOVA compute (non vengono riportati di seguito alcuni WARNING):
>
>
  • Sul Cloud controller verificare lo stato dei servizi Nova compute:
 
# nova-manage service list
Line: 162 to 158
 nova-network stack-03.cnaf.infn.it nova enabled smile 2012-08-31 09:46:25 nova-cert stack-03.cnaf.infn.it nova enabled smile 2012-08-31 09:46:24 nova-volume stack-03.cnaf.infn.it nova enabled smile 2012-08-31 09:46:24
Deleted:
<
<
 
Changed:
<
<
  • You must run the command that creates the network and the bridge using the virbr0 specified in the nova.conf file to create the network that the virtual machines use. This example shows the network range using 192.168.122.0/24 as the fixed range for our guest
VMs, but you can substitute the range for the network you have available. We're labeling it with private in this case.
>
>
  • Creare la sottorete privata, i cui IP verranno assegnati alle istanze delle macchine virtuali, utilizzando l'interfaccia virtuale (nel caso in esempio virbr0). Il seguente comando, ad esempio, crea una sottorete con range 192.168.122.0/24.
 
# nova-manage network create private --multi_host=T --fixed_range_v4=192.168.122.0/24 --bridge_interface=virbr0 --num_networks=1 --network_size=256
Line: 173 to 167
 # nova-manage network list id IPv4 IPv6 start address DNS1 DNS2 VlanID project uuid 1 192.168.122.0/24 None 192.168.122.2 8.8.4.4 None None None 052f9b4b-e6d7-4ad9-a3f1-929e80008372
Deleted:
<
<
 
Changed:
<
<

Configuring Public (Floating) IP Addresses

Private and Public IP Addresses

Every virtual instance is automatically assigned a private IP address. You may optionally assign public IP addresses to instances. OpenStack uses the term floating IP to refer to an IP address (typically public) that can be dynamically added to a running virtual instance. OpenStack Compute uses Network Address Translation (NAT) to assign floating IPs to virtual instances.
>
>

Configurazione degli indirizzi IP (Floating) pubblici

Indirizzi IP pubblici e privati

Ad ogni istanza virtuale viene automaticamente assegnato un IP privato (appartenente alla sottorete creata al punto precedente). E' possibile assegnare indirizzi pubblici alle istanze. In tal caso verificare la presenza della seguente riga nel file nova.conf
 If you plan to use this feature, you must add the following to your nova.conf file to specify which interface the nova-network service will bind public IP addresses to:
public_interface=eth0

Revision 142012-10-11 - EnricoFattibene

Line: 1 to 1
 
META TOPICPARENT name="GestioneOpenstack"
Changed:
<
<

Installing and Configuring the Compute service (NOVA)

>
>

Installazione e configurazione del servizio Compute (NOVA)

 
Changed:
<
<

Configuring the Hypervisor (KVM)

>
>

Configurare l'Hypervisor (KVM)

 
  • Install virtualizzation RPMs
# yum install qemu-kvm qemu-img virt-manager libvirt libvirt-python python-virtinst libvirt-client bridge-utils
Line: 26 to 24
 
Changed:
<
<
  • Configuration requirements with RHEL
    • Ensure auth=no is set in /etc/qpidd.conf.
>
>
  • Requisiti di configurazione per RHEL
    • Assicurarsi che nel file /etc/qpidd.conf sia settato auth=no .
 
    • use the openstack-config package to turn off force DHCP releases: sudo openstack-config --set /etc/nova/nova.conf DEFAULT force_dhcp_release False (Non viene mostrato nessun output ma modificato il file di configurazione.)
    • If you intend to use guest images that don't have a single partition, then allow libguestfs to inspect the image so that files can be injected, by setting: sudo openstack-config --set /etc/nova/nova.conf DEFAULT libvirt_inject_partition -1 (Non viene mostrato nessun output ma modificato il file di configurazione.)

Configuring OpenStack Compute

Changed:
<
<
Da modificare due file:
  • nova.conf
>
>
Da modificare due file in /etc/nova:
 %TWISTY{ mode="div" showlink=" nova.conf " hidelink=" nova.conf "
Changed:
<
<
remember="off" firststart="hide"
>
>
remember="off" firststart="show"
 showimgright="/twiki/pub/TWiki/TWikiDocGraphics/toggleopen.gif" hideimgright="/twiki/pub/TWiki/TWikiDocGraphics/toggleclose.gif" }%
Line: 57 to 56
 #compute_scheduler_driver=nova.scheduler.filter_scheduler.FilterScheduler

# VOLUMES

Changed:
<
<
volume_group = vg_vol01
>
>
volume_group =
 #volume_name_template = volume-%08x iscsi_helper = tgtadm

# DATABASE del Cloud Controller

Changed:
<
<
sql_connection=mysql://nova:XXXXXX@131.154.101.242/nova
>
>
sql_connection=mysql://nova:XXXXXX@hostname1.domain/nova
  # COMPUTE libvirt_type = kvm
Line: 86 to 85
 dhcpbridge_flagfile = /etc/nova/nova.conf firewall_driver = nova.virt.libvirt.firewall.IptablesFirewallDriver # Change my_ip to match each host
Changed:
<
<
my_ip = 131.154.101.186
>
>
my_ip =
 public_interface = eth0 #vlan_interface = eth0 flat_network_bridge = virbr0
Line: 97 to 96
 #novncproxy_base_url=http://192.168.206.130:6080/vnc_auto.html

# Change vncserver_proxyclient_address and vncserver_listen to match each compute host

Changed:
<
<
vncserver_listen = 131.154.101.186 vncserver_proxyclient_address = 131.154.101.186
>
>
vncserver_listen = vncserver_proxyclient_address =
  # Qpid
Changed:
<
<
qpid_hostname = stack-01.cnaf.infn.it
>
>
qpid_hostname =
 rpc_backend = nova.rpc.impl_qpid

# OTHER

Line: 122 to 121
 mode="div" showlink=" api-paste.ini " hidelink=" api-paste.ini "
Changed:
<
<
remember="off" firststart="hide"
>
>
remember="off" firststart="show"
 showimgright="/twiki/pub/TWiki/TWikiDocGraphics/toggleopen.gif" hideimgright="/twiki/pub/TWiki/TWikiDocGraphics/toggleclose.gif" }%
Line: 132 to 131
 [filter:authtoken] paste.filter_factory = keystone.middleware.auth_token:filter_factory service_protocol = http
Changed:
<
<
service_host = 131.154.101.242
>
>
service_host =
 service_port = 5000
Changed:
<
<
auth_host = 131.154.101.242
>
>
auth_host =
 auth_port = 35357 auth_protocol = http
Changed:
<
<
auth_uri = http://131.154.101.242:5000/
>
>
auth_uri = http://:5000/
 admin_tenant_name = service admin_user = nova
Changed:
<
<
admin_password = XXXXXXX
>
>
admin_password =
  </>
<--/twistyPlugin-->

Revision 132012-09-25 - PaoloVeronesi

Line: 1 to 1
 
META TOPICPARENT name="GestioneOpenstack"

Installing and Configuring the Compute service (NOVA)

Line: 177 to 177
 
Added:
>
>

Configuring Public (Floating) IP Addresses

Private and Public IP Addresses

Every virtual instance is automatically assigned a private IP address. You may optionally assign public IP addresses to instances. OpenStack uses the term floating IP to refer to an IP address (typically public) that can be dynamically added to a running virtual instance. OpenStack Compute uses Network Address Translation (NAT) to assign floating IPs to virtual instances.

If you plan to use this feature, you must add the following to your nova.conf file to specify which interface the nova-network service will bind public IP addresses to:

public_interface=eth0
Restart the nova-network service if you change nova.conf while the service is running.

Enabling IP forwarding

By default, the IP forwarding is disabled on most of Linux distributions. The floating IP feature requires the IP forwarding enabled in order to work, you can check if the forwarding is enabled by running the following command:
# sysctl net.ipv4.ip_forward
net.ipv4.ip_forward = 0
In this example, the IP forwarding is disabled. You can enable it on the fly by running the following command:
$ sysctl -w net.ipv4.ip_forward=1
In order to make the changes permanent, edit the /etc/sysctl.conf and update the IP forwarding setting : /verbatim> net.ipv4.ip_forward = 1

Creating a List of Available Floating IP Addresses

Nova maintains a list of floating IP addresses that are available for assigning to instances. Use the nova-manage floating create command to add entries to this list, as root. For example:

nova-manage floating create 131.154.101.220 The following nova-manage commands apply to floating IPs.

  • nova-manage floating list: List the floating IP addresses in the pool.
  • nova-manage floating create [cidr]: Create specific floating IPs for either a single address or a subnet.
  • nova-manage floating delete [cidr]: Remove floating IP addresses using the same parameters as the create command.

Adding a Floating IP to an Instance

Adding a floating IP to an instance is a two step process:
  1. nova floating-ip-create: Allocate a floating IP address from the list of available addresses.
  2. nova add-floating-ip: Add an allocated floating IP address to a running instance.

Here's an example of how to add a floating IP to a running instance with an ID of 63c5b9ba-3308-43ce-af61-d7b5dbc08c15

#  nova floating-ip-create
+-----------------+-------------+----------+------+
|        Ip       | Instance Id | Fixed Ip | Pool |
+-----------------+-------------+----------+------+
| 131.154.101.220 | None        | None     | nova |
+-----------------+-------------+----------+------+

# nova add-floating-ip 63c5b9ba-3308-43ce-af61-d7b5dbc08c15 131.154.101.220

# nova-manage floating list
c10d9c9f296b47f8a1212dd7a98357e0        131.154.101.220 63c5b9ba-3308-43ce-af61-d7b5dbc08c15    nova    eth0

If the instance no longer needs a public address, remove the floating IP address from the instance and de-allocate the address:

# nova remove-floating-ip 63c5b9ba-3308-43ce-af61-d7b5dbc08c15 131.154.101.220
# nova floating-ip-delete 131.154.101.220

Automatically adding floating IPs

The nova-network service can be configured to automatically allocate and assign a floating IP address to virtual instances when they are launched. Add the following line to nova.conf and restart the nova-network service
auto_assign_floating_ip=True

Note that if this option is enabled and all of the floating IP addresses have already been allocated, the nova boot command will fail with an error.

 -- PaoloVeronesi - 2012-08-30

Revision 122012-08-31 - PaoloVeronesi

Line: 1 to 1
 
META TOPICPARENT name="GestioneOpenstack"

Installing and Configuring the Compute service (NOVA)

Line: 166 to 166
 
Added:
>
>
  • You must run the command that creates the network and the bridge using the virbr0 specified in the nova.conf file to create the network that the virtual machines use. This example shows the network range using 192.168.122.0/24 as the fixed range for our guest
VMs, but you can substitute the range for the network you have available. We're labeling it with private in this case.
# nova-manage network create private --multi_host=T --fixed_range_v4=192.168.122.0/24 --bridge_interface=virbr0 --num_networks=1 --network_size=256

# nova-manage network list
id      IPv4                    IPv6            start address   DNS1            DNS2            VlanID          project         uuid           
1       192.168.122.0/24        None            192.168.122.2   8.8.4.4         None            None            None            052f9b4b-e6d7-4ad9-a3f1-929e80008372

 -- PaoloVeronesi - 2012-08-30 \ No newline at end of file

Revision 112012-08-31 - PaoloVeronesi

Line: 1 to 1
 
META TOPICPARENT name="GestioneOpenstack"

Installing and Configuring the Compute service (NOVA)

Line: 10 to 10
  # yum groupinstall Virtualization "Virtualization Client" "Virtualization Platform" "Virtualization Tools"
Changed:
<
<
# yum install openstack-utils memcached qpid-cpp-server openstack-nova dnsmasq-utils
>
>
# yum install openstack-utils memcached qpid-cpp-server openstack-nova dnsmasq-utils python-keystone-auth-token
 

  • Pre-configured the network (di default viene su cos).

Revision 102012-08-31 - PaoloVeronesi

Line: 1 to 1
 
META TOPICPARENT name="GestioneOpenstack"

Installing and Configuring the Compute service (NOVA)

Line: 31 to 31
 
    • use the openstack-config package to turn off force DHCP releases: sudo openstack-config --set /etc/nova/nova.conf DEFAULT force_dhcp_release False (Non viene mostrato nessun output ma modificato il file di configurazione.)
    • If you intend to use guest images that don't have a single partition, then allow libguestfs to inspect the image so that files can be injected, by setting: sudo openstack-config --set /etc/nova/nova.conf DEFAULT libvirt_inject_partition -1 (Non viene mostrato nessun output ma modificato il file di configurazione.)
Added:
>
>

Configuring OpenStack Compute

Da modificare due file:
  • nova.conf
<--/twistyPlugin twikiMakeVisibleInline-->
[DEFAULT]
# LOG/STATE
logdir = /var/log/nova
verbose = True
state_path = /var/lib/nova
lock_path = /var/lib/nova/tmp

# AUTHENTICATION
auth_strategy = keystone

# SCHEDULER
#compute_scheduler_driver=nova.scheduler.filter_scheduler.FilterScheduler

# VOLUMES
volume_group = vg_vol01
#volume_name_template = volume-%08x
iscsi_helper = tgtadm

# DATABASE del Cloud Controller
sql_connection=mysql://nova:XXXXXX@131.154.101.242/nova

# COMPUTE
libvirt_type = kvm
connection_type = libvirt
#instance_name_template = instance-%08x
#api_paste_config=/etc/nova/api-paste.ini
#allow_resize_to_same_host=True

# APIS
#osapi_compute_extension=nova.api.openstack.compute.contrib.standard_extensions
#ec2_dmz_host=192.168.206.130
#s3_host=192.168.206.130

# GLANCE
#image_service=nova.image.glance.GlanceImageService
#glance_api_servers=192.168.206.130:9292

# NETWORK
network_manager = nova.network.manager.FlatDHCPManager
force_dhcp_release = True
dhcpbridge_flagfile = /etc/nova/nova.conf
firewall_driver = nova.virt.libvirt.firewall.IptablesFirewallDriver
# Change my_ip to match each host
my_ip = 131.154.101.186
public_interface = eth0
#vlan_interface = eth0
flat_network_bridge = virbr0
flat_interface = eth0
fixed_range = 192.168.122.0/24

# NOVNC CONSOLE
#novncproxy_base_url=http://192.168.206.130:6080/vnc_auto.html

# Change vncserver_proxyclient_address and vncserver_listen to match each compute host
vncserver_listen = 131.154.101.186
vncserver_proxyclient_address = 131.154.101.186

# Qpid
qpid_hostname = stack-01.cnaf.infn.it
rpc_backend = nova.rpc.impl_qpid

# OTHER
dhcpbridge = /usr/bin/nova-dhcpbridge
injected_network_template = /usr/share/nova/interfaces.template
libvirt_xml_template = /usr/share/nova/libvirt.xml.template
libvirt_nonblocking = True
libvirt_inject_partition = -1
vpn_client_template = /usr/share/nova/client.ovpn.template
credentials_template = /usr/share/nova/novarc.template
root_helper = sudo nova-rootwrap
remove_unused_base_images = True
<--/twistyPlugin-->

  • verificare che in fondo a /etc/nova/api-paste.ini ci siano le seguenti configurazioni (la parte prima non si tocca, 131.154.101.242 l'ip di keystone ).
<--/twistyPlugin twikiMakeVisibleInline-->
[...]

[filter:authtoken]
paste.filter_factory = keystone.middleware.auth_token:filter_factory
service_protocol = http
service_host = 131.154.101.242
service_port = 5000
auth_host = 131.154.101.242
auth_port = 35357
auth_protocol = http
auth_uri = http://131.154.101.242:5000/
admin_tenant_name = service 
admin_user = nova
admin_password = XXXXXXX
<--/twistyPlugin-->

  • lanciare i seguenti comandi:
# for svc in api objectstore compute network volume scheduler cert; do echo openstack-nova-$svc; service openstack-nova-$svc stop ; chkconfig openstack-nova-$svc on; done
 
Added:
>
>
# nova-manage db sync

# for svc in api objectstore compute network volume scheduler cert; do echo openstack-nova-$svc; /etc/init.d/openstack-nova-$svc start ; done

  • Sul Cloud controller, verificare lo stato dei NOVA compute (non vengono riportati di seguito alcuni WARNING):
# nova-manage service list

Binary           Host                                 Zone             Status     State Updated_At
nova-scheduler   stack-03.cnaf.infn.it                nova             enabled    :-)   2012-08-31 09:46:24
nova-compute     stack-03.cnaf.infn.it                nova             enabled    :-)   2012-08-31 09:46:26
nova-network     stack-03.cnaf.infn.it                nova             enabled    :-)   2012-08-31 09:46:25
nova-cert        stack-03.cnaf.infn.it                nova             enabled    :-)   2012-08-31 09:46:24
nova-volume      stack-03.cnaf.infn.it                nova             enabled    :-)   2012-08-31 09:46:24

  -- PaoloVeronesi - 2012-08-30 \ No newline at end of file

Revision 92012-08-30 - PaoloVeronesi

Line: 1 to 1
 
META TOPICPARENT name="GestioneOpenstack"

Installing and Configuring the Compute service (NOVA)

Line: 13 to 13
 # yum install openstack-utils memcached qpid-cpp-server openstack-nova dnsmasq-utils
Deleted:
<
<
Ensure auth=no is set in /etc/qpidd.conf.

# openstack-config --set /etc/nova/nova.conf DEFAULT force_dhcp_release False
Non viene mostrato nessun output ma modificato il file di configurazione.

# openstack-config --set /etc/nova/nova.conf DEFAULT libvirt_inject_partition -1
Non viene mostrato nessun output ma modificato il file di configurazione.
 
  • Pre-configured the network (di default viene su cos).
# ifconfig virbr0
Line: 39 to 26
 
Added:
>
>
  • Configuration requirements with RHEL
    • Ensure auth=no is set in /etc/qpidd.conf.
    • use the openstack-config package to turn off force DHCP releases: sudo openstack-config --set /etc/nova/nova.conf DEFAULT force_dhcp_release False (Non viene mostrato nessun output ma modificato il file di configurazione.)
    • If you intend to use guest images that don't have a single partition, then allow libguestfs to inspect the image so that files can be injected, by setting: sudo openstack-config --set /etc/nova/nova.conf DEFAULT libvirt_inject_partition -1 (Non viene mostrato nessun output ma modificato il file di configurazione.)
 

-- PaoloVeronesi - 2012-08-30 \ No newline at end of file

Revision 82012-08-30 - AndreaCristofori

Line: 1 to 1
 
META TOPICPARENT name="GestioneOpenstack"

Installing and Configuring the Compute service (NOVA)

Line: 20 to 20
  Non viene mostrato nessun output ma modificato il file di configurazione.
Added:
>
>
# openstack-config --set /etc/nova/nova.conf DEFAULT libvirt_inject_partition -1
Non viene mostrato nessun output ma modificato il file di configurazione.
 

  • Pre-configured the network (di default viene su cos).

Revision 72012-08-30 - PaoloVeronesi

Line: 1 to 1
 
META TOPICPARENT name="GestioneOpenstack"

Installing and Configuring the Compute service (NOVA)

Line: 10 to 10
  # yum groupinstall Virtualization "Virtualization Client" "Virtualization Platform" "Virtualization Tools"
Changed:
<
<
# yum install openstack-utils memcached qpid-cpp-server openstack-nova
>
>
# yum install openstack-utils memcached qpid-cpp-server openstack-nova dnsmasq-utils
 

Ensure auth=no is set in /etc/qpidd.conf.

Revision 62012-08-30 - AndreaCristofori

Line: 1 to 1
 
META TOPICPARENT name="GestioneOpenstack"

Installing and Configuring the Compute service (NOVA)

Line: 13 to 13
 # yum install openstack-utils memcached qpid-cpp-server openstack-nova
Added:
>
>
Ensure auth=no is set in /etc/qpidd.conf.

# openstack-config --set /etc/nova/nova.conf DEFAULT force_dhcp_release False
Non viene mostrato nessun output ma modificato il file di configurazione.

 
  • Pre-configured the network (di default viene su cos).
# ifconfig virbr0

Revision 52012-08-30 - PaoloVeronesi

Line: 1 to 1
 
META TOPICPARENT name="GestioneOpenstack"

Installing and Configuring the Compute service (NOVA)

Line: 13 to 13
 # yum install openstack-utils memcached qpid-cpp-server openstack-nova
Changed:
<
<
  • Pre-configuring the network
>
>
  • Pre-configured the network (di default viene su cos).
# ifconfig virbr0
virbr0    Link encap:Ethernet  HWaddr 52:54:00:54:65:A1  
          inet addr:192.168.122.1  Bcast:192.168.122.255  Mask:255.255.255.0
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:45 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0 
          RX bytes:0 (0.0 b)  TX bytes:7585 (7.4 KiB)
 

Revision 42012-08-30 - AndreaCristofori

Line: 1 to 1
 
META TOPICPARENT name="GestioneOpenstack"

Installing and Configuring the Compute service (NOVA)

Line: 9 to 9
 # yum install qemu-kvm qemu-img virt-manager libvirt libvirt-python python-virtinst libvirt-client bridge-utils

# yum groupinstall Virtualization "Virtualization Client" "Virtualization Platform" "Virtualization Tools"

Added:
>
>
# yum install openstack-utils memcached qpid-cpp-server openstack-nova
 
Added:
>
>
 
  • Pre-configuring the network

Revision 32012-08-30 - PaoloVeronesi

Line: 1 to 1
 
META TOPICPARENT name="GestioneOpenstack"

Installing and Configuring the Compute service (NOVA)

Configuring the Hypervisor (KVM)

Changed:
<
<
>
>
  • Install virtualizzation RPMs
 
Changed:
<
<
yum install qemu-kvm qemu-img virt-manager libvirt libvirt-python python-virtinst libvirt-client bridge-utils yum groupinstall Virtualization "Virtualization Client" "Virtualization Platform" "Virtualization Tools"
>
>
# yum install qemu-kvm qemu-img virt-manager libvirt libvirt-python python-virtinst libvirt-client bridge-utils
 
Added:
>
>
# yum groupinstall Virtualization "Virtualization Client" "Virtualization Platform" "Virtualization Tools"
 
Added:
>
>
  • Pre-configuring the network
 

Revision 22012-08-30 - AndreaCristofori

Line: 1 to 1
 
META TOPICPARENT name="GestioneOpenstack"

Installing and Configuring the Compute service (NOVA)

Configuring the Hypervisor (KVM)

Added:
>
>
yum install qemu-kvm qemu-img virt-manager libvirt libvirt-python python-virtinst libvirt-client bridge-utils
yum groupinstall Virtualization "Virtualization Client" "Virtualization Platform" "Virtualization Tools"

 

-- PaoloVeronesi - 2012-08-30 \ No newline at end of file

Revision 12012-08-30 - PaoloVeronesi

Line: 1 to 1
Added:
>
>
META TOPICPARENT name="GestioneOpenstack"

Installing and Configuring the Compute service (NOVA)

Configuring the Hypervisor (KVM)

-- PaoloVeronesi - 2012-08-30

 
This site is powered by the TWiki collaboration platformCopyright © 2008-2019 by the contributing authors. All material on this collaboration platform is the property of the contributing authors.
Ideas, requests, problems regarding TWiki? Send feedback