22/09/2023

Object Storage: Como implementar DELL ECS Virtual Appliance en VMware vSphere

Desde hace algunas semanas vengo jugando con Veeam 12 en mi laboratorio (¡sé que debo el 2do post, ya está llegando!) y una de las features más esperadas (¡claro que si!) es la capacidad de hacer backup directamente a un object storage.

Para probar esta feature utilice 2 object Storage: TRUENAS y Dell ECS Virtual appliance, del cual voy a explicar a continuación como implementarlo.

Lo primero que deben saber es que Dell ECS es un appliance de object storage. Acá pueden ver más información al respecto: https://www.dell.com/es-es/dt/storage/ecs/index.htm#tab0=0&tab1=0

Como claramente no voy a comprar una caja para mis pruebas, decidí a realizar el deploy del appliance virtual en mi laboratorio vSphere. Para llevarlo a cabo seguí la documentación del proyecto: https://github.com/EMCECS/ECS-CommunityEdition/blob/master/docs/source/installation/ECS-Installation.md utilizando la guía de «OVA Installation».

Lo primero que les recomiendo es leer todo el paso a paso y familiarizarse con el mismo. Por mi parte, voy a explicar acá que hice yo, que cosas tuve que «entender» y que cosas tuve que cambiar del mismo para que me funcione.

NOTA: Todo esto post esta basado en el tipo de implementacion «all in one»

1.1. Descargar y realizar el deploy del OVA

Desde este link pueden descargar el ultimo OVA del proyecto: https://github.com/EMCECS/ECS-CommunityEdition/releases

Una vez descargado el mismo, se debe realizar el deploy en vCenter. Es super limitado, por lo cual solo podrán definir el datastore (Thick o Thin provisioning) y la placa de red.

La implementación constara de 2 discos:

  • El primero de 104gb, donde estará toda la «instalación»
  • El segundo de 200gb, es el que usaremos más adelante para crear nuestra partición de object storage.

1.2. Encendido y configuracion de la VM

Acá viene la primera data importante. Hay que encender la VM e ingresar con las siguientes credenciales:

  • User: Root
  • Password: ChangeMe

IMPORTANTE: Una vez dentro es importante ejecutar el comando «sudo nmtui» y configurar los parámetros de red.

1- Editamos una conexion:

2- Seleccionamos la placa de red:

3- Definimos los parametros:

4- Guardamos los cambios.

Al finalizar todos los cambios, hacer un «yum update» y hacer un reboot de la VM.

2. Crear el mapa de Deploy (deploy.yml)

Acá viene lo más importante, configurar bien el archivo «deploy.yml». Logueados como root pueden encontrarlo en:

  • /opt/emc/ecs-install

Hay que usar «vi» o pueden instalar «nano». Pero, para usar todos los comandos es necesario utilizar el usuario de linux «admin». Para esto simplemente tenemos que ejecutar el comando «su admin». En caso de pedir password, la misma es «ChangeMe».

Cuando ingresamos como «admin» tenemos acceso a todas las utilidades, las cuales se especifican en el siguiente link: https://github.com/EMCECS/ECS-CommunityEdition/blob/master/docs/source/utilities/utilities.md

También podemos seguir el paso a paso del git:

  1. Log into the first VM and run videploy. —> Este comando permite directamente definir los parametros.
  2. Edit this deploy.yml file with your favorite editor on another machine, or use vi deploy.yml on the install node. Read the comments in the file and review the examples in the examples/ directory.
  3. Top-level deployment facts (facts:) 0. Enter the IP address of the install node into the install_node: field. 0. Enter into the management_clients: field the CIDR address/mask of each machine or subnet that will be whitelisted in node’s firewalls and allowed to communicate with ECS management API.
    • 10.1.100.50/32 is exactly the IP address.
    • 192.168.2.0/24 is the entire /24 subnet.
    • 0.0.0.0/0 represents the entire Internet.
    • En este paso a paso es clave poner la misma IP que definimos mas arriba con el comando «mntui»
  4. SSH login details (ssh_defaults:) 0. If the SSH server is bound to a non-standard port, enter that port number in the ssh_port: field, or leave it set at the default (22). 0. Enter the username of a user permitted to run commands as UID 0/GID 0 («root») via the sudo command into the ssh_username: field. This must be the same across all nodes. 0. Enter the password for the above user in the ssh_password: field. This will only be used during the initial public key authentication setup and can be changed after. This must be the same across all nodes.—-> Todo esto queda igual
  5. Node configuration (node_defaults:) 0. Enter the DNS domain for the ECS installation. This can simply be set to localdomain if you will not be using DNS with this ECS deployment. 0. Enter each DNS server address, one per line, into dns_servers:. This can be what’s present in /etc/resolv.conf, or it can be a different DNS server entirely. This DNS server will be set to the primary DNS server for each ECS node. 0. Enter each NTP server address, one per line, into ntp_servers:.—–> Super importante tener definido en el AD del laboratorio el nombre DNS y la IP del appliance. En cuanto al NTP,. yo siempre uso los de ar.pool.
  6. Storage Pool configuration (storage_pools:) 0. Enter the storage pool name:. 0. Enter each member data node’s IP address, one per line, in members:. 0. Under options:, enter each block device reserved for ECS, one per line, in ecs_block_devices:. All member data nodes of a storage pool must be identical.—-> Aca es super importante definir en el archivo el disco correcto. En mi caso es el SDB de 200gb. 

Todos los demas parametros son opcionales. Recomiendo no tocarlos.

3. Deploy y configuracion de nodos.

Cuando se guarden los cambios en el archivo «deploy.yml» este se va a actualizar automáticamente, por lo cual ya estas listo para la instalación. En caso de no estar seguros, ejecutar el comando «update_deploy».

El paso siguiente es ejecutar como admin el comando «ova-step1». Una vez finalizado te va a pedir que esperes unos 30 minutos antes de ejecutar el comando que sigue.

Transcurrido ese tiempo, queda el último paso que es ejecutar el comando «ova-step2». El mismo va  pedir unos 15 minutos mas.

¡Una vez finalizado todo el proceso, reiniciamos y estamos listos para utilizar nuestro ECS!

Debemos ingresar via HTTPS a la IP del appliance, con las siguientes credenciales:

  • user: root
  • password: ChangeMe

Por ultimo, les dejo la guia de ECS (version vieja pero sirve) para que puedan tener una referencia a la hora de configurarlo: https://www.delltechnologies.com/asset/en-us/products/storage/technical-support/docu95698.pdf

42 comentarios en «Object Storage: Como implementar DELL ECS Virtual Appliance en VMware vSphere»

  1. These included appraisals of recent systematic reviews to preliminarily identify important evidence gaps, transformation of evidence gaps into research questions and organization of the questions within a comprehensive analytic framework, engagement of stakeholders to identify additional gaps and prioritize research needs or questions, scans of recently published and ongoing studies relevant to the stakeholders list of prioritized research needs, and identification of potential study designs to address prioritized research questions propecia hairline

  2. Black circles indicate each mutation at the specific protein position; numbers in parentheses indicate the total number of samples reported to harbor the specific indicated mutations buy liquid cialis online Also, we have spent a lot of money doing certain tests that were out of pocket, like some blood work and ERA TEST

  3. Thank you for your sharing. I am worried that I lack creative ideas. It is your article that makes me full of hope. Thank you. But, I have a question, can you help me?

  4. Your article made me suddenly realize that I am writing a thesis on gate.io. After reading your article, I have a different way of thinking, thank you. However, I still have some doubts, can you help me? Thanks.

  5. At the beginning, I was still puzzled. Since I read your article, I have been very impressed. It has provided a lot of innovative ideas for my thesis related to gate.io. Thank u. But I still have some doubts, can you help me? Thanks.

  6. At the beginning, I was still puzzled. Since I read your article, I have been very impressed. It has provided a lot of innovative ideas for my thesis related to gate.io. Thank u. But I still have some doubts, can you help me? Thanks.

  7. Thank you very much for sharing. Your article was very helpful for me to build a paper on gate.io. After reading your article, I think the idea is very good and the creative techniques are also very innovative. However, I have some different opinions, and I will continue to follow your reply.

  8. Thank you very much for sharing. Your article was very helpful for me to build a paper on gate.io. After reading your article, I think the idea is very good and the creative techniques are also very innovative. However, I have some different opinions, and I will continue to follow your reply.

  9. Thank you very much for sharing. Your article was very helpful for me to build a paper on gate.io. After reading your article, I think the idea is very good and the creative techniques are also very innovative. However, I have some different opinions, and I will continue to follow your reply.

  10. I am a student of BAK College. The recent paper competition gave me a lot of headaches, and I checked a lot of information. Finally, after reading your article, it suddenly dawned on me that I can still have such an idea. grateful. But I still have some questions, hope you can help me.

  11. I may need your help. I’ve been doing research on gate io recently, and I’ve tried a lot of different things. Later, I read your article, and I think your way of writing has given me some innovative ideas, thank you very much.

  12. Very nice post. I just stumbled upon your blog and wanted to say that I’ve really enjoyed browsing your blog posts. In any case I’ll be subscribing to your feed and I hope you write again soon!

  13. Do you mind if I quote a couple of your articles as long asI provide credit and sources back to your website?My blog site is in the very same niche as yours and my users would certainly benefit from some of the information you present here.Please let me know if this okay with you. Thanks!

Deja una respuesta

Tu dirección de correo electrónico no será publicada. Los campos obligatorios están marcados con *