From 458774a016d9c9c3d04476ceee4d8dca3ea3bba6 Mon Sep 17 00:00:00 2001 From: Vijayalakshmi S Date: Tue, 17 Apr 2018 14:05:15 -0400 Subject: [PATCH 01/15] Added exception handling for create_snapshot and remove_image --- ims/einstein/operations.py | 56 ++++++++++++++++++++++++++++++++++++-- 1 file changed, 53 insertions(+), 3 deletions(-) diff --git a/ims/einstein/operations.py b/ims/einstein/operations.py index 0036e00..51b7d72 100755 --- a/ims/einstein/operations.py +++ b/ims/einstein/operations.py @@ -332,6 +332,7 @@ def deprovision(self, node_name, network, nic): @log def create_snapshot(self, node_name, snap_name): try: + error_flag = [0] self.hil.validate_project(self.proj) ceph_img_name = self.__get_ceph_image_name(node_name) @@ -344,7 +345,7 @@ def create_snapshot(self, node_name, snap_name): is_snapshot=True) snap_ceph_name = self.__get_ceph_image_name(snap_name) self.fs.clone(ceph_img_name, constants.DEFAULT_SNAPSHOT_NAME, - snap_ceph_name) + snap_ceph_name, flag=error_flag) self.fs.flatten(snap_ceph_name) self.fs.snap_image(snap_ceph_name, constants.DEFAULT_SNAPSHOT_NAME) self.fs.snap_protect(snap_ceph_name, @@ -355,10 +356,41 @@ def create_snapshot(self, node_name, snap_name): constants.DEFAULT_SNAPSHOT_NAME) return self.__return_success(True) - except (HILException, DBException, FileSystemException) as e: + except HILException as e: + # Nothing more to do, if HIL validation fails logger.exception('') return self.__return_error(e) + except DBException as e: + # Failure has occured at db insert, unprotect and remove snapshot of ceph img + logger.exception('') + self.fs.snap_unprotect(ceph_img_name, + constants.DEFAULT_SNAPSHOT_NAME) + self.fs.remove_snapshot(ceph_img_name, + constants.DEFAULT_SNAPSHOT_NAME) + time.sleep(constants.HIL_CALL_TIMEOUT) + return self.__return_error(e) + + except FileSystemException as e: + logger.exception('') + # If file system exception occurs: + + # 1. During initial snap creation or snap protect of ceph, then nothing more to do. + + # 2. During clone or beyond such as flattening, snap image or protect of snap ceph image, + # then undo cloning, undo db insert for the given snap name, unprotect and remove + # snapshot of ceph img. + + if error_flag == constants.CLONE: + self.fs.remove(snap_ceph_name) + self.db.image.delete_with_name_from_project(snap_name, self.proj) + self.fs.snap_unprotect(ceph_img_name, + constants.DEFAULT_SNAPSHOT_NAME) + self.fs.remove_snapshot(ceph_img_name, + constants.DEFAULT_SNAPSHOT_NAME) + time.sleep(constants.HIL_CALL_TIMEOUT) + return self.__return_error(e) + # Lists snapshot for the given image img_name # URL's have to be read from BMI config file # fs_obj will be populated by decorator @@ -388,7 +420,25 @@ def remove_image(self, img_name): self.fs.remove(ceph_img_name) self.db.image.delete_with_name_from_project(img_name, self.proj) return self.__return_success(True) - except (HILException, DBException, FileSystemException) as e: + + except HILException as e: + # Nothing more to do, if HIL validation fails + logger.exception('') + return self.__return_error(e) + + except DBException as e: + # Failure has occured at db delete, undo unprotect and remove snapshot of ceph img + logger.exception('') + self.fs.clone(ceph_img_name) + self.fs.snap_image(ceph_img_name, + constants.DEFAULT_SNAPSHOT_NAME) + self.fs.snap_protect(ceph_img_name, + constants.DEFAULT_SNAPSHOT_NAME) + time.sleep(constants.HIL_CALL_TIMEOUT) + return self.__return_error(e) + + except FileSystemException as e: + # Nothing more to do, if file system exception occurs logger.exception('') return self.__return_error(e) From 77635dcc1852a6609f51f1668974871c9f8df0b9 Mon Sep 17 00:00:00 2001 From: Vijayalakshmi S Date: Tue, 17 Apr 2018 14:05:20 -0400 Subject: [PATCH 02/15] Added exception handling for create_snapshot and remove_image --- ims/einstein/ceph.py | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/ims/einstein/ceph.py b/ims/einstein/ceph.py index 4d78f73..2f9495b 100755 --- a/ims/einstein/ceph.py +++ b/ims/einstein/ceph.py @@ -102,8 +102,9 @@ def create_image(self, img_id, img_size): raise file_system_exceptions.FunctionNotSupportedException() @log - def clone(self, parent_img_name, parent_snap_name, clone_img_name): + def clone(self, parent_img_name, parent_snap_name, clone_img_name, flag=None): try: + flag[0] = constants.CLONE parent_context = child_context = self.context self.rbd.clone(parent_context, parent_img_name, parent_snap_name, child_context, clone_img_name, features=1) From 03d0a7ddd3f8b3732929699e21a0ad98fb2d59b3 Mon Sep 17 00:00:00 2001 From: Vijayalakshmi S Date: Tue, 17 Apr 2018 14:06:27 -0400 Subject: [PATCH 03/15] Added exception handling for create_snapshot and remove_image --- ims/common/constants.py | 2 ++ 1 file changed, 2 insertions(+) diff --git a/ims/common/constants.py b/ims/common/constants.py index 353a574..8c321cd 100644 --- a/ims/common/constants.py +++ b/ims/common/constants.py @@ -1,4 +1,6 @@ # Config Flags +CLONE = 1 + PICASSO_CONFIG_FLAG = 'picasso' EINSTEIN_CONFIG_FLAG = 'einstein' From 9a1a67ba2bca5ac0cc2e1149311187e87b397f3d Mon Sep 17 00:00:00 2001 From: Vijayalakshmi S Date: Tue, 17 Apr 2018 14:13:18 -0400 Subject: [PATCH 04/15] Added exception handling for create_snapshot and remove_image --- ims/einstein/operations.py | 1 - 1 file changed, 1 deletion(-) diff --git a/ims/einstein/operations.py b/ims/einstein/operations.py index 51b7d72..f72655d 100755 --- a/ims/einstein/operations.py +++ b/ims/einstein/operations.py @@ -380,7 +380,6 @@ def create_snapshot(self, node_name, snap_name): # 2. During clone or beyond such as flattening, snap image or protect of snap ceph image, # then undo cloning, undo db insert for the given snap name, unprotect and remove # snapshot of ceph img. - if error_flag == constants.CLONE: self.fs.remove(snap_ceph_name) self.db.image.delete_with_name_from_project(snap_name, self.proj) From 2f7c8702a3166b7b6184ef0ad94d89cdbc2dcb81 Mon Sep 17 00:00:00 2001 From: Vijayalakshmi S Date: Tue, 17 Apr 2018 14:30:04 -0400 Subject: [PATCH 05/15] Detailed beginners guide docs --- .../BMI_image_creation.md | 41 ++++ docs/Beginners_guide_docs/BMI_installation.md | 177 ++++++++++++++++++ .../BMI_node_provisioning.md | 59 ++++++ 3 files changed, 277 insertions(+) create mode 100644 docs/Beginners_guide_docs/BMI_image_creation.md create mode 100644 docs/Beginners_guide_docs/BMI_installation.md create mode 100644 docs/Beginners_guide_docs/BMI_node_provisioning.md diff --git a/docs/Beginners_guide_docs/BMI_image_creation.md b/docs/Beginners_guide_docs/BMI_image_creation.md new file mode 100644 index 0000000..00084f1 --- /dev/null +++ b/docs/Beginners_guide_docs/BMI_image_creation.md @@ -0,0 +1,41 @@ + +Generally BMI images are centos, we may be requested for Ubuntu at which point we will need to create BMI ubuntu image as follows. + +1. Download latest requested (Ubuntu) cloud image or server image. + +2. Install dracut +``` + sudo apt install dracut-core +``` + +3. Modify dracut.conf to ensure hostonly=“no” . This ensure that the image is generic, if not the image created would contain only dracut modules/filesystems which are needed to boot the current specific machine. Fracut configuration file may be found in below path in ubuntu case. + +``` + /etc/dracut.conf.d/10-debian.conf + ``` + + 4. If the image is cloud image, disable cloud.init as follows (this ensures cloud based customizations that take longer boot time are disabled), if not skip this step + + ``` + + echo 'datasource_list: [ None ]' | sudo -s tee /etc/cloud/cloud.cfg.d/90_dpkg.cfg + sudo apt-get purge cloud-init + sudo rm -rf /etc/cloud/; sudo rm -rf /var/lib/cloud/ + reboot + +``` + +5. Create image by following command + +``` + Dracut —force +``` + +6. Next add Intel 10 Gig NICs. The following link contains the steps for the same (ubuntu). + +``` + http://ask.xmodulo.com/download-install-ixgbe-driver-ubuntu-debian.html +``` + + + diff --git a/docs/Beginners_guide_docs/BMI_installation.md b/docs/Beginners_guide_docs/BMI_installation.md new file mode 100644 index 0000000..d26e811 --- /dev/null +++ b/docs/Beginners_guide_docs/BMI_installation.md @@ -0,0 +1,177 @@ + +Prerequisties: Ceph (cephargs, ceph.conf, client.bmi.key) and HIl project and network information is already available. + +Description : Installing BMI on a machine would mean to enable a machine to provide BMI services in conjunction with Ceph and HIL (alreayd configued and available as mentioned in pre-requisites). To learn more about BMI architecture and services visit https://github.com/CCI-MOC/ims/blob/master/README.md. To install BMI on a machine ansible software/ansible-playbook script is used. The script installs all the necessary software’s (on the given machine only) to orchestrate the BMI services in conjunction with Ceph and HIL. The following modifications need to be taken care of before ansible script execution. To know more about Ansible scripting/template visit http://docs.ansible.com/. + +Pre-step : Modify ims/constants/common.py file so that the BMI_ADMIN_PROJECT is set to your project (HIL project) to when bootstrapping the database. + +1. Perform the following as sudo su. + +2. Get the latest Ansible playbook scripts repository from Git. The general repository is ~/ims/scripts/install/production/ + + ``` + + git clone https://github.com/CCI-MOC/ims.git + + Eg: The latest scripts at the time of documentation was PR 153. + git fetch origin pull/153/head:pr-153 + git checkout pr-153 +``` + +3. Install Ansible + + a. For Ubuntu: +``` + sudo apt-get update + sudo apt-get install software-properties-common + sudo apt-add-repository ppa:ansible/ansible + sudo apt-get update + sudo apt-get install ansible + + b. For Centos/RHEL: + sudo yum install ansible +``` + +4. Add your host to the ansible hosts file (/etc/ansible/hosts), i.e: + +``` + # Ex 1: Ungrouped hosts, specify before any group headers. + 192.168.122.76 + + Since in this case, we are installing on the local machine itself, the following could be done: + + # Ex 1: Ungrouped hosts, specify before any group headers. + localhost ansible_connection=local +``` + +5. Modify the following sections in bmi_config.cfg under ~/ims + +a. To have a new UID as follows: +``` + [bmi] + uid = + service = + + EG: + [bmi] + uid = vj-test- + service = true +``` + +b. To match your HIL setup as follows: + +``` + [fs] + id = + pool = + conf_file = + + EG: + id = bmi + pool = bmi + conf_file = /etc/ceph/ceph.conf + keyring = /etc/ceph/client.bmi.key + (Note: Modify the id, pool name and paths accordingly.) +``` + +c. To match your Ceph setup as follows: + +``` + # This section is for network isolator (HIL) related config + [net_isolator] + url = + + EG: + [net_isolator] + url = http://192.168.100.210:80/ + (Note: Modify the url according to your HIL endpoint accordingly) +``` + +6. Modify dnsmasq.conf within roles/dhcp/tasks/main.yml. The DHCP range and interface needs to be changed accordingly to match your requirements (below is an example). + +``` + - name: Add DHCP configuration to dnsmasq.conf + lineinfile: + path: /etc/dnsmasq.conf + line: "{{ item }}" + become: true + with_items: + - 'interface=eth2' + - 'dhcp-range=10.10.10.50,10.10.10.100,7d' + - 'dhcp-boot=pxelinux.0' + - 'enable-tftp' + - 'tftp-root=/var/lib/tftpboot' + - 'dhcp-userclass=set:ENH,iPXE' +``` + +Note : Also configure the interface (eth2 in the above ex) to have a gateway IP related to the range of IPs chosen above. Considering the above case, ifcfg-eth2 could have static IP of say 10.10.10.1. + + +7. In roles/bmi/tasks/main.yml: + +a. Modify Ceph and HIL credentials in to the the correct username and password for your configuration. This includes the CEPH_ARGS and HIL_ENDPOINT (below is an example). + +``` + - name: Add Ceph and HIL credentials to bashrc + lineinfile: + path: ~/.bashrc + line: "{{ item }}" + become: true + with_items: + - 'export CEPH_ARGS="--keyring /etc/ceph/client.bmi.key --id bmi --pool bmi"' + - 'export HIL_USERNAME=vj' + - 'export HIL_PASSWORD=redhat' + - 'export HIL_ENDPOINT="http://192.168.100.210:80"' + - 'export BMI_CONFIG=/etc/bmi/bmiconfig.cfg' + +``` + +b. Modify the project project and network from 'bmi_infra' and 'bmi_network' to the project and network you created within HIL (below is an example). + +``` + - name: Bootstrap the database + command: "{{ item }}" + environment: + HIL_USERNAME: vj + HIL_PASSWORD: redhat + with_items: + - bmi db ls + - sqlite3 /etc/bmi/bmi.db "insert into project values (1, 'vj', 'bmi-provision-vj')" + when: db.stat.size == 0 +``` + +8. Comment out any of the roles that you don’t want to execute in site.yml. + +9. Run ansible-playbook site.yml. + + ``` + ansible-playbook site.yml +``` + +10. The install playbook modifies ~/.bashrc. Make sure to refresh your shell after it is run. + + +Possible errors one may face: +------------------------------ + + +1. + +``` +fatal: [localhost]: FAILED! => {"changed": false, "cmd": "/usr/bin/git clone --origin origin https://github.com/fujita/tgt /home/vj/ims/scripts/install/production/tgt", "msg": "fatal: could not create work tree dir '/home/vj/ims/scripts/install/production/tgt'.: Permission denied", "rc": 128, "stderr": "fatal: could not create work tree dir '/home/vj/ims/scripts/install/production/tgt'.: Permission denied\n", "stderr_lines": ["fatal: could not create work tree dir '/home/vj/ims/scripts/install/production/tgt'.: Permission denied"], "stdout": "", "stdout_lines": []}[WARNING]: Could not create retry file '/home/vj/ims/scripts/install/production/site.retry'. [Errno 13] Permission denied: u'/home/vj/ims/scripts/install/production/site.retry' + +``` + +Possible reasons: Not executing as sudo. + + +2. + +``` +Error 4 \nwarning: failed to load external entity \"http://docbook.sourceforge.net/release/xsl/current/manpages/docbook.xsl\" +``` + +Possible reasons: The sourceforge site could be offline or down. Could try again after a while. +(Note: This site is frequently known to be down!. Could think about having these docs stored locally.) + diff --git a/docs/Beginners_guide_docs/BMI_node_provisioning.md b/docs/Beginners_guide_docs/BMI_node_provisioning.md new file mode 100644 index 0000000..1e478b3 --- /dev/null +++ b/docs/Beginners_guide_docs/BMI_node_provisioning.md @@ -0,0 +1,59 @@ +The execution involves the following steps. Please note all the steps below are to be executed as root user. + +1. Start the Picasso (frontend) server as follows: + +``` + >> screen + >> picasso_server + + If successful it should show something like below + * Running on http://10.10.10.1:1513/ (Press CTRL+C to quit) + +``` +2. Start the Einstein (backend) server as follows: +``` + >> screen + >> einstein_server + + If successful it should show something like below + Broadcast server running on 0.0.0.0:9091 + NS running on 10.10.10.1:9893 (10.10.10.1) + Warning: HMAC key not set. Anyone can connect to this server! + URI = PYRO:Pyro.NameServer@10.10.10.1:9893 +``` + +Note : Few errors one could face at this phase + 1. Address already in use : socket error -> This is a well known socket error, killing the process and restarting should resolve it. + +``` + ps aux | grep picasso/einstein + kill -9 +``` + 2. Permission denied : Probably not executing it as root user. + + +3. bmi --help will list down all the bmi commands + +4. To provision a node the command is as follows + +``` + Usage: bmi pro [OPTIONS] PROJECT NODE IMG NETWORK NIC + + EG: bmi pro vj dell-8 centos_67_e1 bmi-provision-vj em1 +``` + + +Possible errors one may face: +------------------------------ + +Enable debug and verbose in bmi_config.cfg. The logs can be found under path "var/log/bmi/" + +1. Connection reject : + Better to try again. + +2. Got status code 409 from HIL with message : + Node not in project : The node assigned to be provisioned has been freed and is no longer part of the (your) project. Need to reacquire it. The link https://github.com/CCI-MOC/kumo-leasing/blob/master/instructions.md has all the necessary information for the same. + +3. Couldn't connect to HIL : + Check logs for reason for HIL connection exception. Test HIL_ENDPOINT connection through ping and curl. If thats fine check further from logs to see where the exception occurred. Some common mistakes include additional or wrong quotes in url in bmi_config.cfg, which result in request.gets error. + From a8e208193efb31b71425e13f0e8ed109c4fc8df3 Mon Sep 17 00:00:00 2001 From: VijayalakshmiVJ <33880328+VijayalakshmiVJ@users.noreply.github.com> Date: Tue, 17 Apr 2018 14:37:31 -0400 Subject: [PATCH 06/15] Update BMI_image_creation.md --- docs/Beginners_guide_docs/BMI_image_creation.md | 14 ++++++++++---- 1 file changed, 10 insertions(+), 4 deletions(-) diff --git a/docs/Beginners_guide_docs/BMI_image_creation.md b/docs/Beginners_guide_docs/BMI_image_creation.md index 00084f1..9d28c49 100644 --- a/docs/Beginners_guide_docs/BMI_image_creation.md +++ b/docs/Beginners_guide_docs/BMI_image_creation.md @@ -1,5 +1,5 @@ -Generally BMI images are centos, we may be requested for Ubuntu at which point we will need to create BMI ubuntu image as follows. +Generally BMI images are centos, we may be requested for debian based images (Ubuntu) at which point we will need to create BMI ubuntu image as follows. 1. Download latest requested (Ubuntu) cloud image or server image. @@ -8,13 +8,13 @@ Generally BMI images are centos, we may be requested for Ubuntu at which point w sudo apt install dracut-core ``` -3. Modify dracut.conf to ensure hostonly=“no” . This ensure that the image is generic, if not the image created would contain only dracut modules/filesystems which are needed to boot the current specific machine. Fracut configuration file may be found in below path in ubuntu case. +3. Modify dracut.conf to ensure hostonly=“no” . This ensures that the image is generic, if not the image created would contain only dracut modules/filesystems which are needed to boot the current machine. Dracut configuration file could be found in below path in ubuntu case. ``` /etc/dracut.conf.d/10-debian.conf ``` - 4. If the image is cloud image, disable cloud.init as follows (this ensures cloud based customizations that take longer boot time are disabled), if not skip this step + 4. If cloud image was taken, disable cloud.init as follows (this ensures cloud based customizations that take longer boot time are disabled), if not skip this step ``` @@ -25,13 +25,19 @@ Generally BMI images are centos, we may be requested for Ubuntu at which point w ``` +or + +``` + touch /etc/cloud/cloud-init.disabled +``` + 5. Create image by following command ``` Dracut —force ``` -6. Next add Intel 10 Gig NICs. The following link contains the steps for the same (ubuntu). +6. Next add Intel 10 Gig NIC. The following link contains the good information for the same (ubuntu). ``` http://ask.xmodulo.com/download-install-ixgbe-driver-ubuntu-debian.html From 146b4d09e3a21a69e0a26820d9f0521bac9adbc6 Mon Sep 17 00:00:00 2001 From: VijayalakshmiVJ <33880328+VijayalakshmiVJ@users.noreply.github.com> Date: Tue, 17 Apr 2018 14:40:36 -0400 Subject: [PATCH 07/15] Update BMI_installation.md --- docs/Beginners_guide_docs/BMI_installation.md | 31 +++++++++---------- 1 file changed, 14 insertions(+), 17 deletions(-) diff --git a/docs/Beginners_guide_docs/BMI_installation.md b/docs/Beginners_guide_docs/BMI_installation.md index d26e811..2a214cf 100644 --- a/docs/Beginners_guide_docs/BMI_installation.md +++ b/docs/Beginners_guide_docs/BMI_installation.md @@ -1,16 +1,13 @@ -Prerequisties: Ceph (cephargs, ceph.conf, client.bmi.key) and HIl project and network information is already available. +Prerequisties: Ceph (cephargs, ceph.conf, client.bmi.key) and HIL project and network information is already available. -Description : Installing BMI on a machine would mean to enable a machine to provide BMI services in conjunction with Ceph and HIL (alreayd configued and available as mentioned in pre-requisites). To learn more about BMI architecture and services visit https://github.com/CCI-MOC/ims/blob/master/README.md. To install BMI on a machine ansible software/ansible-playbook script is used. The script installs all the necessary software’s (on the given machine only) to orchestrate the BMI services in conjunction with Ceph and HIL. The following modifications need to be taken care of before ansible script execution. To know more about Ansible scripting/template visit http://docs.ansible.com/. +Description : Installing BMI on a machine would mean to enable a machine to provide BMI services in conjunction with Ceph and HIL (these are already configued and available as mentioned in pre-requisites). To learn more about BMI architecture and services visit https://github.com/CCI-MOC/ims/blob/master/README.md. To install BMI on a machine ansible software/ansible-playbook script is used. The script installs all the necessary software’s (on the given machine only) to orchestrate the BMI services in conjunction with Ceph and HIL. The following modifications need to be taken care of before ansible script execution. To know more about Ansible scripting/template visit http://docs.ansible.com/. -Pre-step : Modify ims/constants/common.py file so that the BMI_ADMIN_PROJECT is set to your project (HIL project) to when bootstrapping the database. +Pre-step : Modify ims/constants/common.py file so that the BMI_ADMIN_PROJECT is set to your project (HIL project) to when bootstrapping the database. Perform the following as sudo su. -1. Perform the following as sudo su. - -2. Get the latest Ansible playbook scripts repository from Git. The general repository is ~/ims/scripts/install/production/ +1. Get the latest Ansible playbook scripts repository from Git. The general repository is ~/ims/scripts/install/production/ ``` - git clone https://github.com/CCI-MOC/ims.git Eg: The latest scripts at the time of documentation was PR 153. @@ -18,7 +15,7 @@ Pre-step : Modify ims/constants/common.py file so that the BMI_ADMIN_PROJECT is git checkout pr-153 ``` -3. Install Ansible +2. Install Ansible a. For Ubuntu: ``` @@ -32,7 +29,7 @@ Pre-step : Modify ims/constants/common.py file so that the BMI_ADMIN_PROJECT is sudo yum install ansible ``` -4. Add your host to the ansible hosts file (/etc/ansible/hosts), i.e: +3. Add your host to the ansible hosts file (/etc/ansible/hosts), i.e: ``` # Ex 1: Ungrouped hosts, specify before any group headers. @@ -44,7 +41,7 @@ Pre-step : Modify ims/constants/common.py file so that the BMI_ADMIN_PROJECT is localhost ansible_connection=local ``` -5. Modify the following sections in bmi_config.cfg under ~/ims +4. Modify the following sections in bmi_config.cfg under ~/ims a. To have a new UID as follows: ``` @@ -54,8 +51,8 @@ a. To have a new UID as follows: EG: [bmi] - uid = vj-test- - service = true + uid = vj-test- + service = true ``` b. To match your HIL setup as follows: @@ -88,7 +85,7 @@ c. To match your Ceph setup as follows: (Note: Modify the url according to your HIL endpoint accordingly) ``` -6. Modify dnsmasq.conf within roles/dhcp/tasks/main.yml. The DHCP range and interface needs to be changed accordingly to match your requirements (below is an example). +5. Modify dnsmasq.conf within roles/dhcp/tasks/main.yml. The DHCP range and interface needs to be changed accordingly to match your requirements (below is an example). ``` - name: Add DHCP configuration to dnsmasq.conf @@ -108,7 +105,7 @@ c. To match your Ceph setup as follows: Note : Also configure the interface (eth2 in the above ex) to have a gateway IP related to the range of IPs chosen above. Considering the above case, ifcfg-eth2 could have static IP of say 10.10.10.1. -7. In roles/bmi/tasks/main.yml: +6. In roles/bmi/tasks/main.yml: a. Modify Ceph and HIL credentials in to the the correct username and password for your configuration. This includes the CEPH_ARGS and HIL_ENDPOINT (below is an example). @@ -141,15 +138,15 @@ b. Modify the project project and network from 'bmi_infra' and 'bmi_network' when: db.stat.size == 0 ``` -8. Comment out any of the roles that you don’t want to execute in site.yml. +7. Comment out any of the roles that you don’t want to execute in site.yml. -9. Run ansible-playbook site.yml. +8. Run ansible-playbook site.yml. ``` ansible-playbook site.yml ``` -10. The install playbook modifies ~/.bashrc. Make sure to refresh your shell after it is run. +9. The install playbook modifies ~/.bashrc. Make sure to refresh your shell after it is run. Possible errors one may face: From 1658d4d4b488e456af4aa26d907dea7bf587153a Mon Sep 17 00:00:00 2001 From: VijayalakshmiVJ <33880328+VijayalakshmiVJ@users.noreply.github.com> Date: Tue, 17 Apr 2018 14:41:49 -0400 Subject: [PATCH 08/15] Update BMI_installation.md --- docs/Beginners_guide_docs/BMI_installation.md | 11 ++++++----- 1 file changed, 6 insertions(+), 5 deletions(-) diff --git a/docs/Beginners_guide_docs/BMI_installation.md b/docs/Beginners_guide_docs/BMI_installation.md index 2a214cf..b99ce0c 100644 --- a/docs/Beginners_guide_docs/BMI_installation.md +++ b/docs/Beginners_guide_docs/BMI_installation.md @@ -1,9 +1,9 @@ -Prerequisties: Ceph (cephargs, ceph.conf, client.bmi.key) and HIL project and network information is already available. +**Prerequisties**: Ceph (cephargs, ceph.conf, client.bmi.key) and HIL project and network information is already available. -Description : Installing BMI on a machine would mean to enable a machine to provide BMI services in conjunction with Ceph and HIL (these are already configued and available as mentioned in pre-requisites). To learn more about BMI architecture and services visit https://github.com/CCI-MOC/ims/blob/master/README.md. To install BMI on a machine ansible software/ansible-playbook script is used. The script installs all the necessary software’s (on the given machine only) to orchestrate the BMI services in conjunction with Ceph and HIL. The following modifications need to be taken care of before ansible script execution. To know more about Ansible scripting/template visit http://docs.ansible.com/. +**Description** : Installing BMI on a machine would mean to enable a machine to provide BMI services in conjunction with Ceph and HIL (these are already configued and available as mentioned in pre-requisites). To learn more about BMI architecture and services visit https://github.com/CCI-MOC/ims/blob/master/README.md. To install BMI on a machine ansible software/ansible-playbook script is used. The script installs all the necessary software’s (on the given machine only) to orchestrate the BMI services in conjunction with Ceph and HIL. The following modifications need to be taken care of before ansible script execution. To know more about Ansible scripting/template visit http://docs.ansible.com/. -Pre-step : Modify ims/constants/common.py file so that the BMI_ADMIN_PROJECT is set to your project (HIL project) to when bootstrapping the database. Perform the following as sudo su. +**Pre-step** : Modify ims/constants/common.py file so that the BMI_ADMIN_PROJECT is set to your project (HIL project) to when bootstrapping the database. Perform the following as sudo su. 1. Get the latest Ansible playbook scripts repository from Git. The general repository is ~/ims/scripts/install/production/ @@ -24,8 +24,9 @@ Pre-step : Modify ims/constants/common.py file so that the BMI_ADMIN_PROJECT is sudo apt-add-repository ppa:ansible/ansible sudo apt-get update sudo apt-get install ansible - - b. For Centos/RHEL: +``` + b. For Centos/RHEL: +``` sudo yum install ansible ``` From e6cef2b774dad41a16f68c172f04b4e00091e99d Mon Sep 17 00:00:00 2001 From: VijayalakshmiVJ <33880328+VijayalakshmiVJ@users.noreply.github.com> Date: Tue, 17 Apr 2018 14:46:23 -0400 Subject: [PATCH 09/15] Update BMI_installation.md --- docs/Beginners_guide_docs/BMI_installation.md | 136 +++++++++--------- 1 file changed, 68 insertions(+), 68 deletions(-) diff --git a/docs/Beginners_guide_docs/BMI_installation.md b/docs/Beginners_guide_docs/BMI_installation.md index b99ce0c..d8f1a73 100644 --- a/docs/Beginners_guide_docs/BMI_installation.md +++ b/docs/Beginners_guide_docs/BMI_installation.md @@ -8,16 +8,16 @@ 1. Get the latest Ansible playbook scripts repository from Git. The general repository is ~/ims/scripts/install/production/ ``` - git clone https://github.com/CCI-MOC/ims.git + git clone https://github.com/CCI-MOC/ims.git - Eg: The latest scripts at the time of documentation was PR 153. - git fetch origin pull/153/head:pr-153 - git checkout pr-153 + Eg: The latest scripts at the time of documentation was PR 153. + git fetch origin pull/153/head:pr-153 + git checkout pr-153 ``` 2. Install Ansible - a. For Ubuntu: +a. For Ubuntu: ``` sudo apt-get update sudo apt-get install software-properties-common @@ -25,7 +25,7 @@ sudo apt-get update sudo apt-get install ansible ``` - b. For Centos/RHEL: +b. For Centos/RHEL: ``` sudo yum install ansible ``` @@ -33,74 +33,74 @@ 3. Add your host to the ansible hosts file (/etc/ansible/hosts), i.e: ``` - # Ex 1: Ungrouped hosts, specify before any group headers. - 192.168.122.76 + # Ex 1: Ungrouped hosts, specify before any group headers. + 192.168.122.76 - Since in this case, we are installing on the local machine itself, the following could be done: + Since in this case, we are installing on the local machine itself, the following could be done: - # Ex 1: Ungrouped hosts, specify before any group headers. - localhost ansible_connection=local + # Ex 1: Ungrouped hosts, specify before any group headers. + localhost ansible_connection=local ``` 4. Modify the following sections in bmi_config.cfg under ~/ims a. To have a new UID as follows: ``` - [bmi] - uid = - service = + [bmi] + uid = + service = - EG: - [bmi] - uid = vj-test- - service = true + EG: + [bmi] + uid = vj-test- + service = true ``` b. To match your HIL setup as follows: ``` - [fs] - id = - pool = - conf_file = + [fs] + id = + pool = + conf_file = - EG: - id = bmi - pool = bmi - conf_file = /etc/ceph/ceph.conf - keyring = /etc/ceph/client.bmi.key - (Note: Modify the id, pool name and paths accordingly.) + EG: + id = bmi + pool = bmi + conf_file = /etc/ceph/ceph.conf + keyring = /etc/ceph/client.bmi.key + (Note: Modify the id, pool name and paths accordingly.) ``` c. To match your Ceph setup as follows: ``` - # This section is for network isolator (HIL) related config - [net_isolator] - url = + # This section is for network isolator (HIL) related config + [net_isolator] + url = - EG: - [net_isolator] - url = http://192.168.100.210:80/ - (Note: Modify the url according to your HIL endpoint accordingly) + EG: + [net_isolator] + url = http://192.168.100.210:80/ + (Note: Modify the url according to your HIL endpoint accordingly) ``` 5. Modify dnsmasq.conf within roles/dhcp/tasks/main.yml. The DHCP range and interface needs to be changed accordingly to match your requirements (below is an example). ``` - - name: Add DHCP configuration to dnsmasq.conf - lineinfile: - path: /etc/dnsmasq.conf - line: "{{ item }}" - become: true - with_items: - - 'interface=eth2' - - 'dhcp-range=10.10.10.50,10.10.10.100,7d' - - 'dhcp-boot=pxelinux.0' - - 'enable-tftp' - - 'tftp-root=/var/lib/tftpboot' - - 'dhcp-userclass=set:ENH,iPXE' + - name: Add DHCP configuration to dnsmasq.conf + lineinfile: + path: /etc/dnsmasq.conf + line: "{{ item }}" + become: true + with_items: + - 'interface=eth2' + - 'dhcp-range=10.10.10.50,10.10.10.100,7d' + - 'dhcp-boot=pxelinux.0' + - 'enable-tftp' + - 'tftp-root=/var/lib/tftpboot' + - 'dhcp-userclass=set:ENH,iPXE' ``` Note : Also configure the interface (eth2 in the above ex) to have a gateway IP related to the range of IPs chosen above. Considering the above case, ifcfg-eth2 could have static IP of say 10.10.10.1. @@ -111,32 +111,32 @@ Note : Also configure the interface (eth2 in the above ex) to have a gateway IP a. Modify Ceph and HIL credentials in to the the correct username and password for your configuration. This includes the CEPH_ARGS and HIL_ENDPOINT (below is an example). ``` - - name: Add Ceph and HIL credentials to bashrc - lineinfile: - path: ~/.bashrc - line: "{{ item }}" - become: true - with_items: - - 'export CEPH_ARGS="--keyring /etc/ceph/client.bmi.key --id bmi --pool bmi"' - - 'export HIL_USERNAME=vj' - - 'export HIL_PASSWORD=redhat' - - 'export HIL_ENDPOINT="http://192.168.100.210:80"' - - 'export BMI_CONFIG=/etc/bmi/bmiconfig.cfg' + - name: Add Ceph and HIL credentials to bashrc + lineinfile: + path: ~/.bashrc + line: "{{ item }}" + become: true + with_items: + - 'export CEPH_ARGS="--keyring /etc/ceph/client.bmi.key --id bmi --pool bmi"' + - 'export HIL_USERNAME=vj' + - 'export HIL_PASSWORD=redhat' + - 'export HIL_ENDPOINT="http://192.168.100.210:80"' + - 'export BMI_CONFIG=/etc/bmi/bmiconfig.cfg' ``` b. Modify the project project and network from 'bmi_infra' and 'bmi_network' to the project and network you created within HIL (below is an example). ``` - - name: Bootstrap the database - command: "{{ item }}" - environment: - HIL_USERNAME: vj - HIL_PASSWORD: redhat - with_items: - - bmi db ls - - sqlite3 /etc/bmi/bmi.db "insert into project values (1, 'vj', 'bmi-provision-vj')" - when: db.stat.size == 0 + - name: Bootstrap the database + command: "{{ item }}" + environment: + HIL_USERNAME: vj + HIL_PASSWORD: redhat + with_items: + - bmi db ls + - sqlite3 /etc/bmi/bmi.db "insert into project values (1, 'vj', 'bmi-provision-vj')" + when: db.stat.size == 0 ``` 7. Comment out any of the roles that you don’t want to execute in site.yml. From e8b52c9b9702ae6da35c5b0f5a803ec2b0347026 Mon Sep 17 00:00:00 2001 From: VijayalakshmiVJ <33880328+VijayalakshmiVJ@users.noreply.github.com> Date: Tue, 17 Apr 2018 14:48:27 -0400 Subject: [PATCH 10/15] Update BMI_installation.md --- docs/Beginners_guide_docs/BMI_installation.md | 29 ++++++++----------- 1 file changed, 12 insertions(+), 17 deletions(-) diff --git a/docs/Beginners_guide_docs/BMI_installation.md b/docs/Beginners_guide_docs/BMI_installation.md index d8f1a73..48a462d 100644 --- a/docs/Beginners_guide_docs/BMI_installation.md +++ b/docs/Beginners_guide_docs/BMI_installation.md @@ -8,16 +8,16 @@ 1. Get the latest Ansible playbook scripts repository from Git. The general repository is ~/ims/scripts/install/production/ ``` - git clone https://github.com/CCI-MOC/ims.git + git clone https://github.com/CCI-MOC/ims.git - Eg: The latest scripts at the time of documentation was PR 153. - git fetch origin pull/153/head:pr-153 - git checkout pr-153 + Eg: The latest scripts at the time of documentation was PR 153. + git fetch origin pull/153/head:pr-153 + git checkout pr-153 ``` 2. Install Ansible -a. For Ubuntu: + a. For Ubuntu: ``` sudo apt-get update sudo apt-get install software-properties-common @@ -25,7 +25,7 @@ a. For Ubuntu: sudo apt-get update sudo apt-get install ansible ``` -b. For Centos/RHEL: + b. For Centos/RHEL: ``` sudo yum install ansible ``` @@ -44,7 +44,7 @@ b. For Centos/RHEL: 4. Modify the following sections in bmi_config.cfg under ~/ims -a. To have a new UID as follows: + a. To have a new UID as follows: ``` [bmi] uid = @@ -56,7 +56,7 @@ a. To have a new UID as follows: service = true ``` -b. To match your HIL setup as follows: + b. To match your HIL setup as follows: ``` [fs] @@ -73,7 +73,7 @@ b. To match your HIL setup as follows: (Note: Modify the id, pool name and paths accordingly.) ``` -c. To match your Ceph setup as follows: + c. To match your Ceph setup as follows: ``` # This section is for network isolator (HIL) related config @@ -108,7 +108,7 @@ Note : Also configure the interface (eth2 in the above ex) to have a gateway IP 6. In roles/bmi/tasks/main.yml: -a. Modify Ceph and HIL credentials in to the the correct username and password for your configuration. This includes the CEPH_ARGS and HIL_ENDPOINT (below is an example). + a. Modify Ceph and HIL credentials in to the the correct username and password for your configuration. This includes the CEPH_ARGS and HIL_ENDPOINT (below is an example). ``` - name: Add Ceph and HIL credentials to bashrc @@ -125,7 +125,7 @@ a. Modify Ceph and HIL credentials in to the the correct username and passwor ``` -b. Modify the project project and network from 'bmi_infra' and 'bmi_network' to the project and network you created within HIL (below is an example). + b. Modify the project project and network from 'bmi_infra' and 'bmi_network' to the project and network you created within HIL (below is an example). ``` - name: Bootstrap the database @@ -153,9 +153,6 @@ b. Modify the project project and network from 'bmi_infra' and 'bmi_network' Possible errors one may face: ------------------------------ - -1. - ``` fatal: [localhost]: FAILED! => {"changed": false, "cmd": "/usr/bin/git clone --origin origin https://github.com/fujita/tgt /home/vj/ims/scripts/install/production/tgt", "msg": "fatal: could not create work tree dir '/home/vj/ims/scripts/install/production/tgt'.: Permission denied", "rc": 128, "stderr": "fatal: could not create work tree dir '/home/vj/ims/scripts/install/production/tgt'.: Permission denied\n", "stderr_lines": ["fatal: could not create work tree dir '/home/vj/ims/scripts/install/production/tgt'.: Permission denied"], "stdout": "", "stdout_lines": []}[WARNING]: Could not create retry file '/home/vj/ims/scripts/install/production/site.retry'. [Errno 13] Permission denied: u'/home/vj/ims/scripts/install/production/site.retry' @@ -163,9 +160,7 @@ fatal: [localhost]: FAILED! => {"changed": false, "cmd": "/usr/bin/git clone --o Possible reasons: Not executing as sudo. - -2. - + ``` Error 4 \nwarning: failed to load external entity \"http://docbook.sourceforge.net/release/xsl/current/manpages/docbook.xsl\" ``` From dad5ebb0a35acd803a60221dece3e19b40c4cca8 Mon Sep 17 00:00:00 2001 From: VijayalakshmiVJ <33880328+VijayalakshmiVJ@users.noreply.github.com> Date: Tue, 17 Apr 2018 14:49:30 -0400 Subject: [PATCH 11/15] Update BMI_installation.md --- docs/Beginners_guide_docs/BMI_installation.md | 21 +++++++++++-------- 1 file changed, 12 insertions(+), 9 deletions(-) diff --git a/docs/Beginners_guide_docs/BMI_installation.md b/docs/Beginners_guide_docs/BMI_installation.md index 48a462d..bd1c742 100644 --- a/docs/Beginners_guide_docs/BMI_installation.md +++ b/docs/Beginners_guide_docs/BMI_installation.md @@ -1,23 +1,26 @@ -**Prerequisties**: Ceph (cephargs, ceph.conf, client.bmi.key) and HIL project and network information is already available. +**Prerequisties** +Ceph (cephargs, ceph.conf, client.bmi.key) and HIL project and network information is already available. -**Description** : Installing BMI on a machine would mean to enable a machine to provide BMI services in conjunction with Ceph and HIL (these are already configued and available as mentioned in pre-requisites). To learn more about BMI architecture and services visit https://github.com/CCI-MOC/ims/blob/master/README.md. To install BMI on a machine ansible software/ansible-playbook script is used. The script installs all the necessary software’s (on the given machine only) to orchestrate the BMI services in conjunction with Ceph and HIL. The following modifications need to be taken care of before ansible script execution. To know more about Ansible scripting/template visit http://docs.ansible.com/. +**Description** +Installing BMI on a machine would mean to enable a machine to provide BMI services in conjunction with Ceph and HIL (these are already configued and available as mentioned in pre-requisites). To learn more about BMI architecture and services visit https://github.com/CCI-MOC/ims/blob/master/README.md. To install BMI on a machine ansible software/ansible-playbook script is used. The script installs all the necessary software’s (on the given machine only) to orchestrate the BMI services in conjunction with Ceph and HIL. The following modifications need to be taken care of before ansible script execution. To know more about Ansible scripting/template visit http://docs.ansible.com/. -**Pre-step** : Modify ims/constants/common.py file so that the BMI_ADMIN_PROJECT is set to your project (HIL project) to when bootstrapping the database. Perform the following as sudo su. +**Pre-step** +Modify ims/constants/common.py file so that the BMI_ADMIN_PROJECT is set to your project (HIL project) to when bootstrapping the database. Perform the following as sudo su. 1. Get the latest Ansible playbook scripts repository from Git. The general repository is ~/ims/scripts/install/production/ ``` - git clone https://github.com/CCI-MOC/ims.git + git clone https://github.com/CCI-MOC/ims.git - Eg: The latest scripts at the time of documentation was PR 153. - git fetch origin pull/153/head:pr-153 - git checkout pr-153 + Eg: The latest scripts at the time of documentation was PR 153. + git fetch origin pull/153/head:pr-153 + git checkout pr-153 ``` 2. Install Ansible - a. For Ubuntu: + - For Ubuntu: ``` sudo apt-get update sudo apt-get install software-properties-common @@ -25,7 +28,7 @@ sudo apt-get update sudo apt-get install ansible ``` - b. For Centos/RHEL: + - For Centos/RHEL: ``` sudo yum install ansible ``` From ef2d5d601d7864d991be40abf12b187e01f2927b Mon Sep 17 00:00:00 2001 From: VijayalakshmiVJ <33880328+VijayalakshmiVJ@users.noreply.github.com> Date: Tue, 17 Apr 2018 14:50:02 -0400 Subject: [PATCH 12/15] Update BMI_installation.md --- docs/Beginners_guide_docs/BMI_installation.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/docs/Beginners_guide_docs/BMI_installation.md b/docs/Beginners_guide_docs/BMI_installation.md index bd1c742..52577b0 100644 --- a/docs/Beginners_guide_docs/BMI_installation.md +++ b/docs/Beginners_guide_docs/BMI_installation.md @@ -1,11 +1,11 @@ -**Prerequisties** +**Prerequisties**
Ceph (cephargs, ceph.conf, client.bmi.key) and HIL project and network information is already available. -**Description** +**Description**
Installing BMI on a machine would mean to enable a machine to provide BMI services in conjunction with Ceph and HIL (these are already configued and available as mentioned in pre-requisites). To learn more about BMI architecture and services visit https://github.com/CCI-MOC/ims/blob/master/README.md. To install BMI on a machine ansible software/ansible-playbook script is used. The script installs all the necessary software’s (on the given machine only) to orchestrate the BMI services in conjunction with Ceph and HIL. The following modifications need to be taken care of before ansible script execution. To know more about Ansible scripting/template visit http://docs.ansible.com/. -**Pre-step** +**Pre-step**
Modify ims/constants/common.py file so that the BMI_ADMIN_PROJECT is set to your project (HIL project) to when bootstrapping the database. Perform the following as sudo su. 1. Get the latest Ansible playbook scripts repository from Git. The general repository is ~/ims/scripts/install/production/ From 84d8881201fad747a6baa05f2ae9de207db65012 Mon Sep 17 00:00:00 2001 From: VijayalakshmiVJ <33880328+VijayalakshmiVJ@users.noreply.github.com> Date: Tue, 17 Apr 2018 14:50:49 -0400 Subject: [PATCH 13/15] Update BMI_installation.md --- docs/Beginners_guide_docs/BMI_installation.md | 10 +++++----- 1 file changed, 5 insertions(+), 5 deletions(-) diff --git a/docs/Beginners_guide_docs/BMI_installation.md b/docs/Beginners_guide_docs/BMI_installation.md index 52577b0..e298fd9 100644 --- a/docs/Beginners_guide_docs/BMI_installation.md +++ b/docs/Beginners_guide_docs/BMI_installation.md @@ -47,7 +47,7 @@ Modify ims/constants/common.py file so that the BMI_ADMIN_PROJECT is set to your 4. Modify the following sections in bmi_config.cfg under ~/ims - a. To have a new UID as follows: + - To have a new UID as follows: ``` [bmi] uid = @@ -59,7 +59,7 @@ Modify ims/constants/common.py file so that the BMI_ADMIN_PROJECT is set to your service = true ``` - b. To match your HIL setup as follows: + - To match your HIL setup as follows: ``` [fs] @@ -76,7 +76,7 @@ Modify ims/constants/common.py file so that the BMI_ADMIN_PROJECT is set to your (Note: Modify the id, pool name and paths accordingly.) ``` - c. To match your Ceph setup as follows: + - To match your Ceph setup as follows: ``` # This section is for network isolator (HIL) related config @@ -111,7 +111,7 @@ Note : Also configure the interface (eth2 in the above ex) to have a gateway IP 6. In roles/bmi/tasks/main.yml: - a. Modify Ceph and HIL credentials in to the the correct username and password for your configuration. This includes the CEPH_ARGS and HIL_ENDPOINT (below is an example). + - Modify Ceph and HIL credentials in to the the correct username and password for your configuration. This includes the CEPH_ARGS and HIL_ENDPOINT (below is an example). ``` - name: Add Ceph and HIL credentials to bashrc @@ -128,7 +128,7 @@ Note : Also configure the interface (eth2 in the above ex) to have a gateway IP ``` - b. Modify the project project and network from 'bmi_infra' and 'bmi_network' to the project and network you created within HIL (below is an example). + - Modify the project project and network from 'bmi_infra' and 'bmi_network' to the project and network you created within HIL (below is an example). ``` - name: Bootstrap the database From 16ad2c432f52ba08c5a8c9a2740e75b2d2290467 Mon Sep 17 00:00:00 2001 From: VijayalakshmiVJ <33880328+VijayalakshmiVJ@users.noreply.github.com> Date: Tue, 17 Apr 2018 14:52:23 -0400 Subject: [PATCH 14/15] Update BMI_node_provisioning.md --- .../BMI_node_provisioning.md | 24 +++++++++---------- 1 file changed, 12 insertions(+), 12 deletions(-) diff --git a/docs/Beginners_guide_docs/BMI_node_provisioning.md b/docs/Beginners_guide_docs/BMI_node_provisioning.md index 1e478b3..80cb272 100644 --- a/docs/Beginners_guide_docs/BMI_node_provisioning.md +++ b/docs/Beginners_guide_docs/BMI_node_provisioning.md @@ -3,23 +3,23 @@ The execution involves the following steps. Please note all the steps below are 1. Start the Picasso (frontend) server as follows: ``` - >> screen - >> picasso_server + >> screen + >> picasso_server - If successful it should show something like below - * Running on http://10.10.10.1:1513/ (Press CTRL+C to quit) + If successful it should show something like below + * Running on http://10.10.10.1:1513/ (Press CTRL+C to quit) ``` 2. Start the Einstein (backend) server as follows: ``` - >> screen - >> einstein_server + >> screen + >> einstein_server - If successful it should show something like below - Broadcast server running on 0.0.0.0:9091 - NS running on 10.10.10.1:9893 (10.10.10.1) - Warning: HMAC key not set. Anyone can connect to this server! - URI = PYRO:Pyro.NameServer@10.10.10.1:9893 + If successful it should show something like below + Broadcast server running on 0.0.0.0:9091 + NS running on 10.10.10.1:9893 (10.10.10.1) + Warning: HMAC key not set. Anyone can connect to this server! + URI = PYRO:Pyro.NameServer@10.10.10.1:9893 ``` Note : Few errors one could face at this phase @@ -29,7 +29,7 @@ Note : Few errors one could face at this phase ps aux | grep picasso/einstein kill -9 ``` - 2. Permission denied : Probably not executing it as root user. + 2. Permission denied : Probably not executing it as root user. 3. bmi --help will list down all the bmi commands From df50f4ab7b6b7fe5198ecbfd7237b4dc5b3a4d46 Mon Sep 17 00:00:00 2001 From: VijayalakshmiVJ <33880328+VijayalakshmiVJ@users.noreply.github.com> Date: Tue, 17 Apr 2018 14:53:11 -0400 Subject: [PATCH 15/15] Update BMI_node_provisioning.md --- docs/Beginners_guide_docs/BMI_node_provisioning.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/docs/Beginners_guide_docs/BMI_node_provisioning.md b/docs/Beginners_guide_docs/BMI_node_provisioning.md index 80cb272..1aea87e 100644 --- a/docs/Beginners_guide_docs/BMI_node_provisioning.md +++ b/docs/Beginners_guide_docs/BMI_node_provisioning.md @@ -22,14 +22,14 @@ The execution involves the following steps. Please note all the steps below are URI = PYRO:Pyro.NameServer@10.10.10.1:9893 ``` -Note : Few errors one could face at this phase - 1. Address already in use : socket error -> This is a well known socket error, killing the process and restarting should resolve it. +Note : Few errors one could face at this phase
+ - Address already in use : socket error -> This is a well known socket error, killing the process and restarting should resolve it. ``` ps aux | grep picasso/einstein kill -9 ``` - 2. Permission denied : Probably not executing it as root user. + - Permission denied : Probably not executing it as root user. 3. bmi --help will list down all the bmi commands