Pro SysAdmin: Mastering IT Systems Administration requires devotionSharing knowledge, thoughts, how-to and troubleshooting guides, tips and discussions on Cloud computing, Virtualization, Telecom, Networking, Storage, Backup, Hardware, Middleware, Datacenter, Unix, Linux, Windows, Monitoring Systems availability and capacity, Load testing, Java, Php, Software, Office solutions, Printers, Security, Firewall, Load balancers, VPN, Antivirus, and other IT Systems Administration topics. Because you will never stop learning.
This site contains documentation for all Citrix products, including Citrix Virtual Apps and Desktops, Citrix ADC (NetScaler), Citrix StoreFront, Citrix Provisioning, Citrix Machine Creation Services (MCS), Citrix Workspace Environment Management (WEM), and more.
You can filter by product, version, and specific topics.
It includes conceptual information, deployment guides, configuration steps, and command references (primarily PowerShell).
Commonly Used Citrix Command Categories and Examples:
Citrix administration heavily relies on PowerShell, especially for managing Citrix Virtual Apps and Desktops. Citrix ADC (NetScaler) has its own command-line interface (CLI).
I. Citrix Virtual Apps and Desktops (PowerShell Snap-ins/Modules):
Administrators use PowerShell cmdlets from various Citrix snap-ins or modules to manage the environment. Here are some common categories and examples:
Broker (Managing Desktops, Applications, and Sessions):
Get-BrokerApplication: Retrieves a list of published applications.
Get-BrokerDesktop: Retrieves a list of desktops.
Get-BrokerMachine: Retrieves a list of machines (physical or virtual).
Get-BrokerDesktopGroup: Retrieves a list of desktop groups.
Get-BrokerCatalog: Retrieves a list of machine catalogs.
Get-BrokerSession: Retrieves information about active user sessions.
Get-BrokerUser: Retrieves information about users and their sessions.
New-BrokerDesktopGroup: Creates a new desktop group.
New-BrokerMachineCatalog: Creates a new machine catalog.
Add-BrokerUser: Adds a user to a desktop group.
Remove-BrokerUser: Removes a user from a desktop group.
Start-BrokerMachine: Starts a machine.
Stop-BrokerMachine: Stops a machine.
Restart-BrokerMachine: Restarts a machine.
Set-BrokerDesktopGroup: Modifies a desktop group’s properties.
Set-BrokerMachineCatalog: Modifies a machine catalog’s properties.
Get-BrokerController: Retrieves information about Delivery Controllers.
Get-BrokerServiceStatus: Checks the status of Citrix Broker services.
Configuration Logging (Auditing Changes):
Get-ConfigLogConfiguration: Retrieves the configuration logging settings.
Get-ConfigLogData: Retrieves configuration logging data based on criteria.
This cheatsheet provides a quick reference for commonly used commands by Citrix Infrastructure Administrators. Remember that the specific commands you use most often will depend on your environment and responsibilities. Always refer to the official Citrix documentation for detailed information and the latest command syntax.
I. Citrix Virtual Apps and Desktops (PowerShell)
A. Broker (Managing Desktops, Applications, and Sessions)
Getting Information:
Get-BrokerApplication: List published applications.
Get-BrokerDesktop: List desktops.
Get-BrokerMachine: List machines (physical or virtual).
Get-BrokerDesktopGroup: List desktop groups.
Get-BrokerCatalog: List machine catalogs.
Get-BrokerSession: List active user sessions.
Get-BrokerUser: List users and their sessions.
Get-BrokerController: Get Delivery Controller information.
Get-BrokerServiceStatus: Check Citrix Broker service status.
Identify the Citrix Component: Determine which part of the Citrix infrastructure you are working with (e.g., Broker, StoreFront, NetScaler).
Locate the Relevant Section: Find the corresponding section in this cheatsheet.
Find the Command Category: Look for the category that matches your task (e.g., Getting Information, Managing Objects, Network Configuration).
Use the Example Command: Adapt the example command to your specific environment by replacing placeholder values (e.g., “GroupName”, IP addresses, UIDs) with your actual values.
Refer to Documentation: If you need more details or options for a specific command, consult the official Citrix Product Documentation.
This cheatsheet provides a solid foundation for common Citrix administration tasks.
Je fais un SOW et il me faut un script de Migration de VMware vers XenServer , je vais essayer en Python et en Go.
I prepare a SOW and need a script to convert VMs from VMware to XENServer 8 and here is the python and go version.
import subprocess
import time
import os
# #############################################################################
# # De VMware Vers XenServer 8 (Que la Force Soit Avec Vous) #
# #############################################################################
#
# Usage:
# 1. Assurez-vous que la CLI XenCenter ('xe') est installée et configurée sur la machine où ce script sera exécuté.
# - Ensure that the XenCenter CLI ('xe') is installed and configured on the machine where this script will be run.
# 2. Exportez manuellement la machine virtuelle VMware que vous souhaitez migrer au format OVF ou OVA.
# - Manually export the VMware virtual machine you wish to migrate to OVF or OVA format.
# 3. Placez les fichiers exportés dans le répertoire spécifié par la variable 'fer_output_ovf_path'.
# - Place the exported files in the directory specified by the 'fer_output_ovf_path' variable.
# 4. Modifiez les variables de configuration au début de ce script avec les informations de votre environnement.
# - Modify the configuration variables at the beginning of this script with your environment information.
# 5. Exécutez le script Python.
# - Run the Python script.
# 6. Suivez les instructions à l'écran et vérifiez la progression dans XenCenter.
# - Follow the on-screen instructions and monitor the progress in XenCenter.
# 7. Effectuez les étapes de post-migration manuelles dans XenCenter une fois l'importation terminée.
# - Perform the manual post-migration steps in XenCenter once the import is complete.
#
# Prérequis:
# - Accès à l'environnement VMware. - Access to the VMware environment.
# - Accès à l'environnement XenServer 8. - Access to the XenServer 8 environment.
# - XenCenter CLI installé et configuré. - XenCenter CLI installed and configured.
# - Python 3 installé sur la machine d'exécution. - Python 3 installed on the execution machine.
#
# Configuration (Pour faciliter la lecture, toutes les variables commencent par "fer") - Configuration (To facilitate reading the code, all variables start with "fer"):
fer_xenserver_host = "your_xenserver_ip" # Remplacez par l'IP de votre XenServer - Replace with your XenServer IP
fer_xenserver_username = "root" # Remplacez par l'utilisateur XenServer - Replace with XenServer user
fer_xenserver_password = "your_xenserver_password" # Remplacez par le mot de passe XenServer - Replace with XenServer password
fer_target_sr_uuid = "your_xenserver_storage_repository_uuid" # Trouvez ceci dans XenCenter ou via 'xe sr-list' - Find this in XenCenter or via 'xe sr-list'
fer_output_ovf_path = "/tmp/vmware_export" # Emplacement temporaire pour l'export OVF (si manuel) - Temporary location for OVF export (if manual)
fer_converted_vhd_path = "/tmp/converted_disk.vhd" # Emplacement temporaire pour le disque converti - Temporary location for converted disk
# --- Helper Functions ---
def run_command(command):
"""Exécute une commande shell et affiche la sortie. - Executes a shell command and prints output.
May the output be ever in your favor, jeune Padawan."""
print(f"Executing: {' '.join(command)}")
process = subprocess.Popen(command, stdout=subprocess.PIPE, stderr=subprocess.PIPE)
stdout, stderr = process.communicate()
if stdout:
print(stdout.decode())
if stderr:
print(f"Error: {stderr.decode()}")
return process.returncode == 0
def wait_for_task(fer_task_uuid):
"""Attend qu'une tâche XenServer se termine. - Waits for a XenServer task to complete.
Patience, jeune Jedi, la Force est lente parfois."""
while True:
result = subprocess.run(['xe', 'task-status', 'uuid=' + fer_task_uuid], capture_output=True, text=True)
if "SUCCESS" in result.stdout:
print(f"Task {fer_task_uuid} completed successfully. Que la Force soit avec vous!")
return True
elif "ERROR" in result.stdout:
print(f"Task {fer_task_uuid} failed: {result.stdout}. C'est une trahison!")
return False
time.sleep(5)
# --- Step 1: Detection of the VM to be converted ---
print("--- Étape 1: Détection de la VM à convertir - Step 1: Detection of the VM to be converted ---")
fer_vmware_vm_name = input("Entrez le nom de la machine virtuelle VMware à migrer (tel qu'il apparaît dans vCenter) : - Enter the name of the VMware virtual machine to migrate (as it appears in vCenter): ")
print(f"VMware VM à migrer : {fer_vmware_vm_name}. - VMware VM to migrate: {fer_vmware_vm_name}.")
print("A long time ago in a galaxy not so far away (your VMware environment)...")
# --- Step 2: Presentation of the conversion plan ---
print("\n--- Étape 2: Présentation du plan de conversion - Step 2: Presentation of the conversion plan ---")
print("Notre plan d'attaque, tel un Wampa affamé, est le suivant : - Our plan of attack, like a hungry Wampa, is as follows:")
print(" 1. Vous allez exporter manuellement la VM VMware '{}' au format OVF ou OVA vers le répertoire : '{}'.".format(fer_vmware_vm_name, fer_output_ovf_path))
print(" - You will manually export the VMware VM '{}' to OVF or OVA format to the directory: '{}'.".format(fer_vmware_vm_name, fer_output_ovf_path))
print(" (C'est comme s'échapper de la base Starkiller, mais avec des fichiers.) - (It's like escaping Starkiller Base, but with files.)")
print(" 2. Nous allons ensuite importer ce fichier OVF/OVA directement dans XenServer '{}' en utilisant la commande 'xe vm-import'.".format(fer_xenserver_host))
print(" - We will then import this OVF/OVA file directly into XenServer '{}' using the 'xe vm-import' command.".format(fer_xenserver_host))
print(" (Préparez-vous pour un saut hyperespace vers XenServer !) - (Prepare for a hyperspace jump to XenServer!)")
input("Appuyez sur Entrée une fois l'exportation OVF/OVA terminée. - Press Enter once the OVF/OVA export is complete...")
# --- Step 3: Ask for Xen VM disk type and size ---
print("\n--- Étape 3: Configuration du disque de la VM Xen - Step 3: Xen VM disk configuration ---")
fer_xen_disk_type = input("Quel type de disque Xen VM souhaitez-vous utiliser ? (thin/thick) : - What type of Xen VM disk do you want to use? (thin/thick): ").lower()
while fer_xen_disk_type not in ["thin", "thick"]:
print("Choix invalide. Veuillez choisir 'thin' ou 'thick'. - Invalid choice. Please choose 'thin' or 'thick'.")
fer_xen_disk_type = input("Quel type de disque Xen VM souhaitez-vous utiliser ? (thin/thick) : - What type of Xen VM disk do you want to use? (thin/thick): ").lower()
while True:
fer_xen_disk_size_gb_str = input("Quelle taille de disque souhaitez-vous pour la VM Xen (en Go) ? - What disk size do you want for the Xen VM (in GB)? ")
try:
fer_xen_disk_size_gb = int(fer_xen_disk_size_gb_str)
if fer_xen_disk_size_gb > 0:
break
else:
print("La taille du disque doit être supérieure à zéro. - Disk size must be greater than zero.")
except ValueError:
print("Veuillez entrer une valeur numérique pour la taille du disque. - Please enter a numeric value for the disk size.")
print(f"Type de disque Xen VM choisi : {fer_xen_disk_type}. - Chosen Xen VM disk type: {fer_xen_disk_type}.")
print(f"Taille du disque Xen VM choisie : {fer_xen_disk_size_gb} Go. - Chosen Xen VM disk size: {fer_xen_disk_size_gb} GB.")
print("La Force est puissante avec vous pour ces choix !")
# --- Step 4: Importing OVF/OVA to XenServer ---
print("\n--- Étape 4: Importation de l'OVF/OVA vers XenServer - Step 4: Importing OVF/OVA to XenServer ---")
fer_final_vm_name = "Migrated-" + fer_vmware_vm_name
import_command = [
"xe", "vm-import",
"filename=" + os.path.join(fer_output_ovf_path, os.listdir(fer_output_ovf_path)[0]), # Tentative de prendre le premier fichier dans le répertoire - Attempts to take the first file in the directory
"sr=" + fer_target_sr_uuid,
"name-label=" + fer_final_vm_name,
"preserve=true", # Préserver l'adresse MAC si possible - Preserve MAC address if possible
"--username", fer_xenserver_username,
"--password", fer_xenserver_password,
"--host", fer_xenserver_host
]
# --- Investigation approfondie et exemples pour le type et la taille du disque ---
print("\n# --- Investigation approfondie sur le type et la taille du disque lors de l'importation ---")
print("# Directement spécifier le type de disque ('thin' ou 'thick') lors de l'importation OVF/OVA avec 'xe vm-import' peut être limité.")
print("# La prise en charge dépend fortement de la façon dont les informations de disque sont encodées dans le package OVF/OVA.")
print("# - Deep dive on disk type ('thin' or 'thick') during import -")
print("# Directly specifying the disk type ('thin' or 'thick') during OVF/OVA import with 'xe vm-import' can be limited.")
print("# Support heavily depends on how the disk information is encoded in the OVF/OVA package.")
print("#")
print("# Possibilités et exemples (peuvent varier selon la version de XenServer 8 et le format OVF/OVA) :")
print("# - Possibilities and examples (may vary depending on XenServer 8 version and OVF/OVA format):")
print("#")
print("# 1. Paramètres VDI (peu probable que cela fonctionne directement pour le type lors de l'importation OVF/OVA) :")
print("# - VDI Parameters (unlikely to work directly for type during OVF/OVA import):")
# import_command.extend(["vdi-params:type=" + fer_xen_disk_type]) # Ceci pourrait ne pas fonctionner directement - This might not work directly
print("# Exemple (Example): # import_command.extend(['vdi-params:type=user']) # 'user' est le type par défaut")
print("#")
print("# 2. Taille virtuelle du VDI (peut être interprétée comme une indication de la taille) :")
print("# - Virtual VDI size (might be interpreted as an indication of size):")
# import_command.extend(["vdi-params:virtual_size=" + str(fer_xen_disk_size_gb * 1024 * 1024 * 1024)]) # La taille est en octets - Size is in bytes
print(f"# Exemple (Example): # import_command.extend(['vdi-params:virtual_size={fer_xen_disk_size_gb * 1024 * 1024 * 1024}'])")
print("#")
print("# 3. Examiner le fichier .ovf : Le fichier descripteur .ovf dans le package OVF/OVA contient des informations sur les disques.")
print("# Vous devrez peut-être examiner ce fichier pour comprendre comment la taille et le provisionnement sont spécifiés.")
print("# - Examine the .ovf file: The .ovf descriptor file in the OVF/OVA package contains information about the disks.")
print("# You might need to examine this file to understand how size and provisioning are specified.")
print("#")
print("# 4. Utilisation des fonctionnalités de stockage XenServer 8 :")
print("# - Using XenServer 8 storage features:")
print("# - XenServer 8 introduit potentiellement des améliorations dans la façon dont le stockage est géré, y compris StorageLink pour l'intégration avec les baies de stockage externes.")
print("# - Si votre 'fer_target_sr_uuid' correspond à un SR sur un stockage externe via StorageLink, les caractéristiques de ce stockage (y compris le provisionnement fin si pris en charge par la baie) peuvent être utilisées lors de l'importation.")
print("# - XenServer 8 potentially introduces improvements in how storage is managed, including StorageLink for integration with external storage arrays.")
print("# - If your 'fer_target_sr_uuid' corresponds to an SR on external storage via StorageLink, the characteristics of that storage (including thin provisioning if supported by the array) might be used during import.")
print("#")
print("# 5. Étapes post-importation (méthode recommandée pour un contrôle précis) :")
print("# - Post-import steps (recommended method for precise control):")
print("# - La méthode la plus fiable pour définir explicitement le type de disque (thin/thick) est de modifier la VM après l'importation à l'aide des commandes 'xe vdi-param-set' et 'xe vbd-param-set'.")
print("# - The most reliable method to explicitly set the disk type (thin/thick) is to modify the VM after import using the 'xe vdi-param-set' and 'xe vbd-param-set' commands.")
print("# - Exemple pour convertir un VDI en provisionnement fin (après avoir trouvé l'UUID du VDI) :")
print("# - Example to convert a VDI to thin provisioning (after finding the VDI UUID):")
print("# # xe vdi-param-set uuid=<VDI_UUID> storage-policy=0 # 0 pour le provisionnement fin")
print("# - Vous pouvez également redimensionner le disque après l'importation si nécessaire.")
print("# - You can also resize the disk after import if needed.")
print("#")
print("# Exemples de combinaisons OVF/OVA et XenServer 8 :")
print("# - OVF/OVA provenant de VMware avec des disques provisionnés en mode 'thin' peuvent être importés dans XenServer avec un provisionnement fin par défaut.")
print("# - OVF/OVA provenant de VMware avec des disques provisionnés en mode 'thick' peuvent être importés dans XenServer avec un provisionnement épais par défaut.")
print("# - Cependant, le comportement exact peut varier en fonction de la version de l'outil d'exportation VMware et de la version de XenServer 8.")
print("# - Il est recommandé de tester l'importation d'une VM de test pour observer le comportement par défaut et ajuster la configuration après l'importation si nécessaire.")
print("# - OVF/OVA from VMware with 'thin' provisioned disks might be imported into XenServer with thin provisioning by default.")
print("# - OVF/OVA from VMware with 'thick' provisioned disks might be imported into XenServer with thick provisioning by default.")
print("# - However, the exact behavior can vary depending on the VMware export tool version and the XenServer 8 version.")
print("# - It is recommended to test the import of a test VM to observe the default behavior and adjust the configuration after import if needed.")
print("#")
print("# Conclusion de l'investigation : Pour un contrôle précis du type et de la taille du disque, il est préférable de vérifier et de modifier la configuration de la VM APRÈS l'importation dans XenServer.")
print("# - Investigation conclusion: For precise control over disk type and size, it's best to verify and modify the VM configuration AFTER importing into XenServer.")
print(f"Commande d'importation générée : {' '.join(import_command)}")
if run_command(import_command):
print(f"L'importation de la VM '{fer_final_vm_name}' vers XenServer a été initiée. Vérifiez XenCenter pour la progression. - VM import of '{fer_final_vm_name}' to XenServer has been initiated. Check XenCenter for progress.")
print("N'ayez pas peur de la puissance du côté obscur... euh, je voulais dire de XenServer !")
else:
print("Erreur lors de l'importation de l'OVF/OVA. Vous devrez peut-être essayer l'importation manuelle via XenCenter ou la méthode de téléchargement du disque. - Error during OVF/OVA import. You might need to try manual import via XenCenter or the disk upload method.")
print("Ce n'est pas la méthode Jedi que nous recherchions...")
# --- Step 5: Post-Migration Configuration (Manual) ---
print("\n--- Étape 5: Configuration post-migration (Manuelle) - Step 5: Post-Migration Configuration (Manual) ---")
print(f"Veuillez vous connecter au XenServer '{fer_xenserver_host}' en utilisant XenCenter. - Please log in to the XenServer '{fer_xenserver_host}' using XenCenter.")
print(f"Localisez la VM migrée nommée '{fer_final_vm_name}'. - Locate the migrated VM named '{fer_final_vm_name}'.")
print("Effectuez les étapes manuelles suivantes dans XenCenter : - Perform the following manual steps in XenCenter:")
print(" 1. Installez les outils VM XenServer sur la VM migrée. - Install XenServer VM Tools on the migrated VM.")
print(" (C'est comme donner à votre VM un sabre laser flambant neuf !) - (It's like giving your VM a brand new lightsaber!)")
print(" 2. Vérifiez et ajustez les paramètres réseau si nécessaire. - Verify and adjust network settings if necessary.")
print(" (Assurez-vous que votre VM peut joindre la rébellion... euh, le réseau !) - (Make sure your VM can join the rebellion... uh, the network!)")
print(" 3. Démarrez la VM et vérifiez le bon fonctionnement des applications. - Start the VM and verify application functionality.")
print(" (Que la Force soit avec votre VM ! Et vos applications aussi.) - (May the Force be with your VM! And your applications too.)")
print(" 4. (Facultatif) Vérifiez et modifiez le type de disque (thin/thick) et la taille dans les propriétés de la VM XenServer ou via la CLI 'xe'.")
print(" - (Optional) Verify and modify the disk type (thin/thick) and size in the XenServer VM properties or via the 'xe' CLI.")
print(" (Utilisez les commandes 'xe vdi-list' pour trouver l'UUID du VDI, puis 'xe vdi-param-set' pour modifier les paramètres.)")
print(" - (Use the 'xe vdi-list' command to find the VDI UUID, then 'xe vdi-param-set' to modify parameters.)")
print("\nProcessus de migration esquissé. Veuillez vérifier XenCenter pour l'état de l'importation. - Migration process outlined. Please check XenCenter for the status of the import.")
Code en Langage GO
package main
import (
"bufio"
"fmt"
"os"
"os/exec"
"strconv"
"strings"
"time"
)
// #############################################################################
// # LA BIBLE DE LA MIGRATION #
// # De VMware Vers XenServer 8 (Que la Force Soit Avec Vous) #
// #############################################################################
//
// Usage:
// 1. Assurez-vous que la CLI XenCenter ('xe') est installée et configurée sur la machine où ce script sera exécuté.
// - Ensure that the XenCenter CLI ('xe') is installed and configured on the machine where this script will be run.
// 2. Exportez manuellement la machine virtuelle VMware que vous souhaitez migrer au format OVF ou OVA.
// - Manually export the VMware virtual machine you wish to migrate to OVF or OVA format.
// 3. Placez les fichiers exportés dans le répertoire spécifié par la variable 'ferOutputOvfPath'.
// - Place the exported files in the directory specified by the 'ferOutputOvfPath' variable.
// 4. Modifiez les variables de configuration au début de ce script avec les informations de votre environnement.
// - Modify the configuration variables at the beginning of this script with your environment information.
// 5. Exécutez le script Go.
// - Run the Go script.
// 6. Suivez les instructions à l'écran et vérifiez la progression dans XenCenter.
// - Follow the on-screen instructions and monitor the progress in XenCenter.
// 7. Effectuez les étapes de post-migration manuelles dans XenCenter une fois l'importation terminée.
// - Perform the manual post-migration steps in XenCenter once the import is complete.
//
// Prérequis:
// - Accès à l'environnement VMware. - Access to the VMware environment.
// - Accès à l'environnement XenServer 8. - Access to the XenServer 8 environment.
// - XenCenter CLI installé et configuré. - XenCenter CLI installed and configured.
// - Go installé sur la machine d'exécution. - Go installed on the execution machine.
//
// Configuration (Toutes les variables doivent commencer par "fer") - Configuration (All variables must start with "fer"):
var ferXenserverHost = "your_xenserver_ip" // Remplacez par l'IP de votre XenServer - Replace with your XenServer IP
var ferXenserverUsername = "root" // Remplacez par l'utilisateur XenServer - Replace with XenServer user
var ferXenserverPassword = "your_xenserver_password" // Remplacez par le mot de passe XenServer - Replace with XenServer password
var ferTargetSrUuid = "your_xenserver_storage_repository_uuid" // Trouvez ceci dans XenCenter ou via 'xe sr-list' - Find this in XenCenter or via 'xe sr-list'
var ferOutputOvfPath = "/tmp/vmware_export" // Emplacement temporaire pour l'export OVF (si manuel) - Temporary location for OVF export (if manual)
var ferConvertedVhdPath = "/tmp/converted_disk.vhd" // Emplacement temporaire pour le disque converti - Temporary location for converted disk
func runCommand(command []string) bool {
"""Exécute une commande shell et affiche la sortie. - Executes a shell command and prints output.
May the output be ever in your favor, jeune Padawan."""
fmt.Printf("Executing: %s\n", strings.Join(command, " "))
cmd := exec.Command(command[0], command[1:]...)
cmd.Stdout = os.Stdout
cmd.Stderr = os.Stderr
err := cmd.Run()
if err != nil {
fmt.Printf("Error executing command: %v\n", err)
return false
}
return true
}
func waitForTask(ferTaskUuid string) bool {
"""Attend qu'une tâche XenServer se termine. - Waits for a XenServer task to complete.
Patience, jeune Jedi, la Force est lente parfois."""
for {
cmd := exec.Command("xe", "task-status", "uuid="+ferTaskUuid)
output, err := cmd.CombinedOutput()
if err != nil {
fmt.Printf("Error getting task status: %v\n", err)
return false
}
outputStr := string(output)
if strings.Contains(outputStr, "SUCCESS") {
fmt.Printf("Task %s completed successfully. Que la Force soit avec vous!\n", ferTaskUuid)
return true
} else if strings.Contains(outputStr, "ERROR") {
fmt.Printf("Task %s failed: %s. C'est une trahison!\n", ferTaskUuid, outputStr)
return false
}
time.Sleep(5 * time.Second)
}
}
func main() {
reader := bufio.NewReader(os.Stdin)
// --- Step 1: Detection of the VM to be converted ---
fmt.Println("--- Étape 1: Détection de la VM à convertir - Step 1: Detection of the VM to be converted ---")
fmt.Print("Entrez le nom de la machine virtuelle VMware à migrer (tel qu'il apparaît dans vCenter) : - Enter the name of the VMware virtual machine to migrate (as it appears in vCenter): ")
ferVmwareVmName, _ := reader.ReadString('\n')
ferVmwareVmName = strings.TrimSpace(ferVmwareVmName)
fmt.Printf("VMware VM à migrer : %s. - VMware VM to migrate: %s.\n", ferVmwareVmName, ferVmwareVmName)
fmt.Println("Un long time ago in a galaxy not so far away (your VMware environment)...")
// --- Step 2: Presentation of the conversion plan ---
fmt.Println("\n--- Étape 2: Présentation du plan de conversion - Step 2: Presentation of the conversion plan ---")
fmt.Println("Notre plan d'attaque, tel un Wampa affamé, est le suivant : - Our plan of attack, like a hungry Wampa, is as follows:")
fmt.Printf(" 1. Vous allez exporter manuellement la VM VMware '%s' au format OVF ou OVA vers le répertoire : '%s'.\n", ferVmwareVmName, ferOutputOvfPath)
fmt.Printf(" - You will manually export the VMware VM '%s' to OVF or OVA format to the directory: '%s'.\n", ferVmwareVmName, ferOutputOvfPath)
fmt.Println(" (C'est comme s'échapper de la base Starkiller, mais avec des fichiers.) - (It's like escaping Starkiller Base, but with files.)")
fmt.Print("Appuyez sur Entrée une fois l'exportation OVF/OVA terminée. - Press Enter once the OVF/OVA export is complete...")
reader.ReadString('\n')
// --- Step 3: Ask for Xen VM disk type and size ---
fmt.Println("\n--- Étape 3: Configuration du disque de la VM Xen - Step 3: Xen VM disk configuration ---")
var ferXenDiskType string
for {
fmt.Print("Quel type de disque Xen VM souhaitez-vous utiliser ? (thin/thick) : - What type of Xen VM disk do you want to use? (thin/thick): ")
ferXenDiskType, _ = reader.ReadString('\n')
ferXenDiskType = strings.TrimSpace(strings.ToLower(ferXenDiskType))
if ferXenDiskType == "thin" || ferXenDiskType == "thick" {
break
}
fmt.Println("Choix invalide. Veuillez choisir 'thin' ou 'thick'. - Invalid choice. Please choose 'thin' or 'thick'.")
}
var ferXenDiskSizeGb int
for {
fmt.Print("Quelle taille de disque souhaitez-vous pour la VM Xen (en Go) ? - What disk size do you want for the Xen VM (in GB)? ")
ferXenDiskSizeGbStr, _ := reader.ReadString('\n')
ferXenDiskSizeGbStr = strings.TrimSpace(ferXenDiskSizeGbStr)
size, err := strconv.Atoi(ferXenDiskSizeGbStr)
if err == nil && size > 0 {
ferXenDiskSizeGb = size
break
}
fmt.Println("Veuillez entrer une valeur numérique valide pour la taille du disque. - Please enter a valid numeric value for the disk size.")
}
fmt.Printf("Type de disque Xen VM choisi : %s. - Chosen Xen VM disk type: %s.\n", ferXenDiskType, ferXenDiskType)
fmt.Printf("Taille du disque Xen VM choisie : %d Go. - Chosen Xen VM disk size: %d GB.\n", ferXenDiskSizeGb, ferXenDiskSizeGb)
fmt.Println("La Force est puissante avec vous pour ces choix !")
// --- Step 4: Importing OVF/OVA to XenServer ---
fmt.Println("\n--- Étape 4: Importation de l'OVF/OVA vers XenServer - Step 4: Importing OVF/OVA to XenServer ---")
ferFinalVmName := "Migrated-" + ferVmwareVmName
var importCommand []string
importCommand = append(importCommand, "xe", "vm-import")
// Tentative de prendre le premier fichier dans le répertoire - Attempts to take the first file in the directory
files, err := os.ReadDir(ferOutputOvfPath)
if err == nil && len(files) > 0 {
importCommand = append(importCommand, "filename="+ferOutputOvfPath+"/"+files[0].Name())
} else {
fmt.Println("Erreur lors de la lecture du répertoire OVF/OVA ou aucun fichier trouvé. Veuillez vérifier le chemin d'accès. - Error reading OVF/OVA directory or no files found. Please check the path.")
return
}
importCommand = append(importCommand, "sr="+ferTargetSrUuid)
importCommand = append(importCommand, "name-label="+ferFinalVmName)
importCommand = append(importCommand, "preserve=true") // Préserver l'adresse MAC si possible - Preserve MAC address if possible
importCommand = append(importCommand, "--username", ferXenserverUsername)
importCommand = append(importCommand, "--password", ferXenserverPassword)
importCommand = append(importCommand, "--host", ferXenserverHost)
// --- Investigation approfondie et exemples pour le type et la taille du disque ---
fmt.Println("\n# --- Investigation approfondie sur le type et la taille du disque lors de l'importation ---")
fmt.Println("# Directement spécifier le type de disque ('thin' ou 'thick') lors de l'importation OVF/OVA avec 'xe vm-import' peut être limité.")
fmt.Println("# La prise en charge dépend fortement de la façon dont les informations de disque sont encodées dans le package OVF/OVA.")
fmt.Println("# - Deep dive on disk type ('thin' or 'thick') during import -")
fmt.Println("# Directly specifying the disk type ('thin' or 'thick') during OVF/OVA import with 'xe vm-import' can be limited.")
fmt.Println("# Support heavily depends on how the disk information is encoded in the OVF/OVA package.")
fmt.Println("#")
fmt.Println("# Possibilités et exemples (peuvent varier selon la version de XenServer 8 et le format OVF/OVA) :")
fmt.Println("# - Possibilities and examples (may vary depending on XenServer 8 version and OVF/OVA format):")
fmt.Println("#")
fmt.Println("# 1. Paramètres VDI (peu probable que cela fonctionne directement pour le type lors de l'importation OVF/OVA) :")
fmt.Println("# - VDI Parameters (unlikely to work directly for type during OVF/OVA import):")
// importCommand = append(importCommand, "vdi-params:type="+ferXenDiskType) // Ceci pourrait ne pas fonctionner directement - This might not work directly
fmt.Println("# Exemple (Example): # importCommand = append(importCommand, \"vdi-params:type=user\") # 'user' est le type par défaut")
fmt.Println("#")
fmt.Println("# 2. Taille virtuelle du VDI (peut être interprétée comme une indication de la taille) :")
fmt.Println("# - Virtual VDI size (might be interpreted as an indication of size):")
// importCommand = append(importCommand, "vdi-params:virtual_size="+strconv.Itoa(ferXenDiskSizeGb*1024*1024*1024)) // La taille est en octets - Size is in bytes
fmt.Printf("# Exemple (Example): # importCommand = append(importCommand, \"vdi-params:virtual_size=%d\")\n", ferXenDiskSizeGb*1024*1024*1024)
fmt.Println("#")
fmt.Println("# 3. Examiner le fichier .ovf : Le fichier descripteur .ovf dans le package OVF/OVA contient des informations sur les disques.")
fmt.Println("# Vous devrez peut-être examiner ce fichier pour comprendre comment la taille et le provisionnement sont spécifiés.")
fmt.Println("# - Examine the .ovf file: The .ovf descriptor file in the OVF/OVA package contains information about the disks.")
fmt.Println("# You might need to examine this file to understand how size and provisioning are specified.")
fmt.Println("#")
fmt.Println("# 4. Utilisation des fonctionnalités de stockage XenServer 8 :")
fmt.Println("# - Using XenServer 8 storage features:")
fmt.Println("# - XenServer 8 introduit potentiellement des améliorations dans la façon dont le stockage est géré, y compris StorageLink pour l'intégration avec les baies de stockage externes.")
fmt.Println("# - Si votre 'ferTargetSrUuid' correspond à un SR sur un stockage externe via StorageLink, les caractéristiques de ce stockage (y compris le provisionnement fin si pris en charge par la baie) peuvent être utilisées lors de l'importation.")
fmt.Println("# - XenServer 8 potentially introduces improvements in how storage is managed, including StorageLink for integration with external storage arrays.")
fmt.Println("# - If your 'ferTargetSrUuid' corresponds to an SR on external storage via StorageLink, the characteristics of that storage (including thin provisioning if supported by the array) might be used during import.")
fmt.Println("#")
fmt.Println("# 5. Étapes post-importation (méthode recommandée pour un contrôle précis) :")
fmt.Println("# - Post-import steps (recommended method for precise control):")
fmt.Println("# - La méthode la plus fiable pour définir explicitement le type de disque (thin/thick) est de modifier la VM après l'importation à l'aide des commandes 'xe vdi-param-set' et 'xe vbd-param-set'.")
fmt.Println("# - The most reliable method to explicitly set the disk type (thin/thick) is to modify the VM after import using the 'xe vdi-param-set' and 'xe vbd-param-set' commands.")
fmt.Println("# - Exemple pour convertir un VDI en provisionnement fin (après avoir trouvé l'UUID du VDI) :")
fmt.Println("# - Example to convert a VDI to thin provisioning (after finding the VDI UUID):")
fmt.Println("# # xe vdi-param-set uuid=<VDI_UUID> storage-policy=0 # 0 pour le provisionnement fin")
fmt.Println("# - Vous pouvez également redimensionner le disque après l'importation si nécessaire.")
fmt.Println("# - You can also resize the disk after import if needed.")
fmt.Println("#")
fmt.Println("# Exemples de combinaisons OVF/OVA et XenServer 8 :")
fmt.Println("# - OVF/OVA provenant de VMware avec des disques provisionnés en mode 'thin' peuvent être importés dans XenServer avec un provisionnement fin par défaut.")
fmt.Println("# - OVF/OVA provenant de VMware avec des disques provisionnés en mode 'thick' peuvent être importés dans XenServer avec un provisionnement épais par défaut.")
fmt.Println("# - Cependant, le comportement exact peut varier en fonction de la version de l'outil d'exportation VMware et de la version de XenServer 8.")
fmt.Println("# - Il est recommandé de tester l'importation d'une VM de test pour observer le comportement par défaut et ajuster la configuration après l'importation si nécessaire.")
fmt.Println("# - OVF/OVA from VMware with 'thin' provisioned disks might be imported into XenServer with thin provisioning by default.")
fmt.Println("# - OVF/OVA from VMware with 'thick' provisioned disks might be imported into XenServer with thick provisioning by default.")
fmt.Println("# - However, the exact behavior can vary depending on the VMware export tool version and the XenServer 8 version.")
fmt.Println("# - It is recommended to test the import of a test VM to observe the default behavior and adjust the configuration after import if needed.")
fmt.Println("#")
fmt.Println("# Conclusion de l'investigation : Pour un contrôle précis du type et de la taille du disque, il est préférable de vérifier et de modifier la configuration de la VM APRÈS l'importation dans XenServer.")
fmt.Println("# - Investigation conclusion: For precise control over disk type and size, it's best to verify and modify the VM configuration AFTER importing into XenServer.")
fmt.Printf("Commande d'importation générée : %s\n", strings.Join(importCommand, " "))
if runCommand(importCommand) {
fmt.Printf("L'importation de la VM '%s' vers XenServer a été initiée. Vérifiez XenCenter pour la progression. - VM import of '%s' to XenServer has been initiated. Check XenCenter for progress.\n", ferFinalVmName, ferFinalVmName)
fmt.Println("N'ayez pas peur de la puissance du côté obscur... euh, je voulais dire de XenServer !")
} else {
fmt.Println("Erreur lors de l'importation de l'OVF/OVA. Vous devrez peut-être essayer l'importation manuelle via XenCenter ou la méthode de téléchargement du disque. - Error during OVF/OVA import. You might need to try manual import via XenCenter or the disk upload method.")
fmt.Println("Ce n'est pas la méthode Jedi que nous recherchions...")
}
// --- Step 5: Post-Migration Configuration (Manual) ---
fmt.Println("\n--- Étape 5: Configuration post-migration (Manuelle) - Step 5: Post-Migration Configuration (Manual) ---")
fmt.Printf("Veuillez vous connecter au XenServer '%s' en utilisant XenCenter. - Please log in to the XenServer '%s' using XenCenter.\n", ferXenserverHost, ferXenserverHost)
fmt.Printf("Localisez la VM migrée nommée '%s'. - Locate the migrated VM named '%s'.\n", ferFinalVmName, ferFinalVmName)
fmt.Println("Effectuez les étapes manuelles suivantes dans XenCenter : - Perform the following manual steps in XenCenter:")
fmt.Println(" 1. Installez les outils VM XenServer sur la VM migrée. - Install XenServer VM Tools on the migrated VM.")
fmt.Println(" (C'est comme donner à votre VM un sabre laser flambant neuf !) - (It's like giving your VM a brand new lightsaber!)")
fmt.Println(" 2. Vérifiez et ajustez les paramètres réseau si nécessaire. - Verify and adjust network settings if necessary.")
fmt.Println(" (Assurez-vous que votre VM peut joindre la rébellion... euh, le réseau !) - (Make sure your VM can join the rebellion... uh, the network!)")
fmt.Println(" 3. Démarrez la VM et vérifiez le bon fonctionnement des applications. - Start the VM and verify application functionality.")
fmt.Println(" (Que la Force soit avec votre VM ! Et vos applications aussi.) - (May the Force be with your VM! And your applications too.)")
fmt.Println(" 4. (Facultatif) Vérifiez et modifiez le type de disque (thin/thick) et la taille dans les propriétés de la VM XenServer ou via la CLI 'xe'.")
fmt.Println(" - (Optional) Verify and modify the disk type (thin/thick) and size in the XenServer VM properties or via the 'xe' CLI.")
fmt.Println(" (Utilisez les commandes 'xe vdi-list' pour trouver l'UUID du VDI, puis 'xe vdi-param-set' pour modifier les paramètres.)")
fmt.Println(" - (Use the 'xe vdi-list' command to find the VDI UUID, then 'xe vdi-param-set' to modify parameters.)")
fmt.Println("\nProcessus de migration esquissé. Veuillez vérifier XenCenter pour l'état de l'importation. - Migration process outlined. Please check XenCenter for the status of the import.")
}
Continuing from Cabling a basic Cloud Computing Infrastructure 1, having connected all the required cabling in the back of the rack mounted server, we did secure all cables using some cabling ties, we need to make sure cables will not be disconnected by mistake when this server is going to be eventually pulled and pushed back inside the cabinet for maintenance.
Back of rack mounted server when completely pulled out of the cabinet. All cables must remain tightly secure in place.
Speaking of pull and push, this is the next step we review in this major “step 2” required when you are installing a rack mounted server on a cabinet (server rack) located in your office or at a remote data center.
It is simple but critical: you need to pull the rack-mounted server completely out of the cabinet as if you need to open the cover and access the motherboard/RAM/CPU/internal hard disks.
Back of rack mounted server view from bottom when completely pulled out of the cabinet. All cables must remain tightly secure in place.
This is to extend the cables to their maximum possible length you will ever need, it allows to start inserting cables in the management arm and properly distributing them inside the Cable management arm in a way they are slightly separated.
View from the back of the rack, this server is in between 2 other servers no space wasted.
I have seen so many installation not fully maximizing their space usage in data centers or IT computer rooms and all of them because they did not took the time to properly organize their cabling. Maybe they were too exited to put the thing online and have other sort of fun.
The point is that as time goes on, more servers come in and you will rarely have time to “rearrange” that space and you could start to get something like this….and this is nothing compared to what I have seen.
Bad and good cabling examples
What do you server room or server cabinet looks like ? I would love to have some Pictures, maybe we should start a server room picture contest or some youtube pimp my rack reality show. lol
TIPS from PROSYSADMIN:
Buy a Roll of velcro, Cabling Identification TABS and various sizes of Cable ties.
Buy Cable management arm for server and for your top of rack (minimum)
Try to use cables of different colors to differentiate between various Network Segments (LAN, DMZ, iSCSI, etc)
Installing server rackmount and cabling is the first step you must complete
Do not do this alone, you need one helper (good team building opportunity)
Good cabling pictures from PROSYSADMIN (Job in Montreal Datacenter - 2009)
Entertainment industry websites and U.S. government agency VICTIMS of Coordinated Distributed Denial-of-Service (DDoS) attacks taking place using a version of a well know tool in the hacker community, L O I C , the Low Orbit Ion Cannon tool. The “SOCIAL” side of this new version of LOIC allows to contribute to a “DDoS Attack” using JavaScript embedded in a webpage.
Various sources have confirmed that a loosely affiliated collective “Anonymous” allegedly promoted the attacks in response to the shutdown of the file hosting site MegaUpload and in protest of the proposed U.S. legislation Stop Online Piracy Act, or SOPA, and Preventing Real Online Threats to Economic Creativity and Theft of Intellectual Property Act, or PIPA.
Here follows my quick analysis of 4 variations of attacks observed during tests with the tool and the equivalent rules to use in the popular security tool snort. Snort is an open source network intrusion prevention system ( IPS ) capable of performing real-time traffic analysis and packet logging on IP networks.
(scroll to the end of the post for a link to the Tweet from the Author of the tool, YouTube video of the messages from Operation Payback and more)
The Javascript version request generated by this LOIC tool looks like this:
GET /app/?id=1292337572944&msg=BOOM%2520HEADSHOT! HTTP/1.1
Host: http://www.site.com
User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.5; en-US; rv:1.9.2.12) Gecko/20101026 Firefox/3.6.12
Accept: text/html,application/xhtml+xml,application/xml;q=0.9,*/*;q=0.8
Accept-Language: en-us,en;q=0.5
Accept-Encoding: gzip,deflate
Accept-Charset: ISO-8859-1,utf-8;q=0.7,*;q=0.7
Keep-Alive: 115
Connection: keep-alive
Many connections in a short period of time will be observed in Ethereal.
SNORT RULE
Since theid field and msg field are present, we can use them in the detection rule as follows:
alert tcp $EXTERNAL_NET any -> $HOME_NET $HTTP_PORTS (msg:”SLR – LOIC DoS Tool JS Version”;
flow: established,to_server ; uricontent:”id=”; uricontent:”msg=”; threshold: type threshold,
track by_src, count 20 , seconds 5; reference: url, http://www.simpleweb.org/reports/loic-report.pdf;
classtype:misc-activity; sid:1234568; rev:1;) The binary version of LOIC has three methods of attack HTTP, UDP and TCP
HTTP Attack:
This version is the easiest to detect since it generates a malformed GET request
GET /HTTP/1.0\r\n
loic http attack packet capture from Wireshark sample
Check for many connections in a short period of time when analyzing UDP traffic. It can be at any port, by default tool uses port 80 but it can be any port.
TCP Attack:
Very similar to UDP but detection based on a keyword is going to be difficult but in Wireshark you can look for ACK TCP flag set and Packets size of 1448.
Sample Wireshark packet capture of TCP attack using LOIC
Maybe you heard denial-of-service (DOS) attacks targeting websites, but you can be a victim of these attacks too. Denial-of-service (DOS) attacks can be somehow difficult to distinguish from the normal network activity, but there are some clear indications that an attack is in progress.
Cabling is one of the most underestimated activities, make sure you do it right the first time because you will not have time to come back and make it better after.
TIPS:
Use 2 cable tags to identify cables at each end; Use cable ties of various sizes to secure cables.
Use 2 cable tags to identify cables at each end; Use cable ties of various sizes to secure cables.
When you are going to need to service that server you need to be sure you will not bring down other servers because you pulled the wrong cable, or when you pull the server it disconnects cables from another server.
Stay tuned for the rest of this series where we will overview the steps involved in building a small private local cloud IaaS (Infrastructure as a Service) on your IT closet or at the Datacenter of your choice, maybe you are lucky and have a great room for your servers.
The Chinese Year, the year of the Dragon begins today monday and many celebrations are taking place all over the world within the Chinese community.
The Lunar New Year is a cyclical system based on a lunisolar calendar, with New Year’s day appearing on the 2nd new moon after the winter solstice. This is why the date varies from year to year, ranging from the end of January through the middle of February.
We count 12 twelve Chinese year-based horoscopes, starting with the Rat follows the Ox, Tiger, Rabbit, Dragon, Snake, Horse, Goat, Monkey, Rooster, Dog and finally the Pig.
The Chinese holiday traditions include forgiving past conflicts, setting off fireworks, hosting elaborate feasts and giving money to children in RED envelopes. The Year of the Dragon is believed to bring success and happiness, while other animals bring other blessings during their years. This celebrations lasts 15 days after New Year’s, and on the final day there is a lantern festival that takes place, red lanterns are hung outside houses all over China.
If you were born in the Year of the Dragon (1940, 1952, 1964, 1976, 1988, 2000), or in any another year, this new year means something for you:
According to the Chinese Zodiac and astrologers this New Year is a “Water Dragon Year” which means a higher flow of communication between people (I guess they predicted the boom of social media 😉 ). The predictions are that Year of the Dragon is one of high risks and high returns; a year during which financial crisis will finally see some light.
You may want to consult the Chinese animal horoscopes or an astrologer to learn more about the predictions your Chinese Zodiac in this Water Dragon Year and I am sure you will find plety if you just search the Internet. I just wanted to share this on my new Blog which I started this Water Dragon Year and I wish a high flow of communication and traffic.
The lunisolar Chinese calendar determines the date of Chinese New Year. The calendar is also used in countries that have adopted or have been influenced by Han culture, notably the Koreans, Japanese and Vietnamese, and may have a common ancestry with the similar New Year festivals outside East Asia, such as Iran, and historically, the Bulgars lands.
The first day is for the welcoming of the deities of the heavens and earth, officially beginning at midnight. Many people, especially Buddhists, abstain from meat consumption on the first day because it is believed that this will ensure longevityfor them. Some consider lighting fires and using knives to be bad luck on New Year’s Day, so all food to be consumed is cooked the days before. On this day, it is considered bad luck to clean.
Most importantly, the first day of Chinese New Year is a time to honor one’s elders and families visit the oldest and most senior members of their extended families, usually their parents, grandparents and great-grandparents.
For Buddhists, the first day is also the birthday of MaitreyaBodhisattva (better known as the more familiar Budai Luohan), the Buddha-to-be. People also abstain from killing animals.
Some families may invite a lion dance troupe as a symbolic ritual to usher in the Chinese New Year as well as to evict bad spirits from the premises. Members of the family who are married also give red envelopes containing cash to junior members of the family, mostly children and teenagers. Business managers also give bonuses through red envelopes to employees for good luck and wealth.
While fireworks and firecrackers are traditionally very popular, some regions have banned them due to concerns over fire hazards, which have resulted in increased number of fires around New Years and challenged municipal fire departments’ work capacity. For this reason, various city governments (e.g., Hong Kong, and Beijing, for a number of years) issued bans over fireworks and firecrackers in certain premises of the city. As a substitute, large-scale fireworks have been launched by governments in such cities as Hong Kong.
SOPA, PIPA, everyone is now talking against it now but we predicted this issue months ago as the technical aspects were being discussed.
If we talk about alternatives: should we be considering a fork of the Internet in 2012, a new Parallel Internet.
This new Internet could be built using exclusively IPv6 allocated addresses which could be controlled as vehicle plates are controlled today; clear laws, copyright regulations and built in security should be essential characteristics of this new Internet.
Using a device such as a dual headed router/firewall, users or business can connect and reach both Internets, or stay out of the Internet we know today.
All Business and Copyrighted material should move to that new Internet, they have the money to build it, let them pay for it.
SOPA, PIPA = every one is manifesting against it but do you understand why ?
Maybe the general public is just missinformed and following some social networks starting movements and propagating STOP SOPA/PIPA trends.
Some companies switched from supporting to NOT supporting SOPA because they started to loose customers and they were scared of having their image affected in a negative way (from a sales and marketing point of view) if they start supporting SOPA/PIPA.
Ask your self: If I am against SOPA/PIPA, doest it mean I am supporting Piracy and Intellectual Property violation ?
Do you know about artists or software authors that have been affected by online piracy ?
I think that the moment the “NET NEUTRALITY” debate began years ago was the moment the net neutrality debate was lost. I do support NET NEUTRALITY, but the main point here is that SOPA/PIPA is completely different. SOPA/PIPA is about solving the problem of online piracy by banning known offenders of Intellectual Property, people distributing copyrighted material that has not been authorized for redistribution by the author.
What I do not support about SOPA/PIPA are the potential abuses of the power some entities will gain, the potential bad procedures or a potential technology not mature enough in a way that could create problems and block the wrong sites.
Instead of expending so much money on these Bills, they should invest some of that money in technology that will make advancement in the area of IP protection.
In all cases, support for online anti-piracy legislation is going to strongly consolidate as the bills progress, enabling it to become law in congressional session. They will require actual website blocking or traffic filtering and with some fixes they will make sure that the legislation will only target ROUGE websites and it will not create unintended problems.
The PROTECT IP Act is a re-write of the Combating Online Infringement and Counterfeits Act (COICA), which failed to pass in 2010. A similar House version of the bill, the Stop Online Piracy Act (SOPA), was introduced on October 26, 2011.
In the wake of online protests held on January 18, 2012, Senate Majority Leader Harry Reid announced that a vote on the bill would be postponed until issues raised about the bill were resolved
The PROTECT IP Act (Preventing Real Online Threats to Economic Creativity and Theft of Intellectual Property Act, or PIPA) is a proposed law with the stated goal of giving the US government and copyright holders additional tools to curb access to “rogue websites dedicated to infringing or counterfeit goods”, especially those registered outside the U.S. The bill was introduced on May 12, 2011, by Senator Patrick Leahy (D-VT) and 11 bipartisan co-sponsors. The Congressional Budget Office estimated that implementation of the bill would cost the federal government $47 million through 2016, to cover enforcement costs and the hiring and training of 22 new special agents and 26 support staff. The Senate Judiciary Committee passed the bill, but Senator Ron Wyden (D-OR) placed a hold on it.
