Develop ancillaryrh7 #368

lel99999 · 2019-05-03T19:47:44Z

CentOS6 -> RHEL7.x

umask -> umask = 022 (normal user - default dir permissions 775, file permissions 664, root - 755/644)
devtools -> devtools-7
open_office -> open_office 4.1.6
evince -> evince 3
stattransfer -> stattransfer 14 (stlinux64_install)
sublime -> sublime 3 (build 34207 x86_64)
texlive -> texlive (latest)
ultra-edit -> ultra-edit 18.0-0.40 (x86_64)

Require free developer subscription: https://developers.redhat.com/blog/2016/03/31/no-cost-rhel-developer-subscription-now-available/

sign-up for developer subscription
create file ~/RHACCOUNT which is referenced in deployment file to register VM on RHN and enable RHN Repo. Add following to ~/RHACCOUNT:
_uid: <name>@<domain>
_pwd: <pwd>

stirlingv · 2019-05-29T18:46:35Z

deploy/deploy_ancillaryRH7.yml

+    - name: Extract repo to destination point
+      shell:  tar xvf /tmp/ancilRH7_repo.tar.gz -C /opt/ancillary_local
+    - name: Extract OpenOffice 4.1.6 
+      shell:  tar xvf /opt/ancillary_local/Apache_OpenOffice_4.1.6_Linux_x86-64_install-rpm_en-US.tar.gz -C /opt/ancillary_local/OO416 


@lel99999 I think these tar files should be in the /artifacts folder on the jenkins machine

stirlingv · 2019-05-29T18:50:17Z

deploy/deploy_ancillaryRH7.yml

@@ -0,0 +1,142 @@
+- hosts: wdcreancil02


@lel99999 I think we want to merge this into the deploy_researcher_environment.yml file, and either add these tasks as roles in the research_ancillary_services hosts section, or make a new section for research_ancillary_services_rh7.

stirlingv · 2019-05-29T18:51:13Z

deploy/deploy_ancillaryRH7.yml

+      command: "/usr/bin/subscription-manager register --username {{ _uid }} --password {{ _pwd }} --auto-attach"
+      when: _uid != "" and _pwd != ""
+#     command: "/usr/bin/subscription-manager register --username <name> --password <password> --auto-attach"
+    - name: register RHEL7 repo


@lel99999 is this necessary in prod, or should we be using the satellite managed by SE?

stirlingv · 2019-05-29T18:52:53Z

deploy/deploy_ancillaryRH7.yml

+      shell:  tar xvf /opt/ancillary_local/sublime_text_3_build_3207_x64.tar.bz2 -C /opt/ancillary_local/Sublime3
+
+    - name: Extract Sublime3 to install dir
+      shell:  tar xvf /opt/ancillary_local/sublime_text_3_build_3207_x64.tar.bz2 -C /usr/local/sublime 


@lel99999 should there be 2 extract tasks for sublime??

Also, shouldn't we be using the existing sublime role? or a new sublime_rhe7 one if the install is different/requires other dependencies for rh7?

stirlingv · 2019-05-29T18:53:38Z

deploy/deploy_ancillaryRH7.yml

+        name=localrepo
+        baseurl=file:///opt/ancillary_local/OO416
+        enabled=1
+        gpgcheck=0' >> /etc/yum.repos.d/local.repo


@lel99999 What is the local repo for?

the local repo duplicates the /artifacts functionality ... will upload there and mark as resolved.

stirlingv · 2019-05-29T19:19:16Z

deploy/deploy_ancillaryRH7.yml

+      shell:  wget https://dl.fedoraproject.org/pub/epel/epel-release-latest-7.noarch.rpm -O /tmp/epel-release-latest-7.noarch.rpm   
+    - name: Install epel
+      shell:  yum -y localinstall /tmp/epel*rpm
+


Are these dependencies or part of the Ancillary services? Might be a good idea to group all dependencies that can be yum installed, and adding them in one task and using with_items:

have added an epel7 role, so will replace this with that role

stirlingv · 2019-05-29T19:19:58Z

deploy/deploy_ancillaryRH7.yml

+#       name: python27-python-pip
+#       state: latest
+    - name: Install python 3.6 and pip
+      shell: yum install -y python36 python36-pip


Shouldn't we be calling the python3 role for this, not installing python separately?

this is a specific directive for RHEL7, it could be placed in a role, but we probably would have to make more fine-grained than python3, probably will have to spell out python3.6, etc.

stirlingv · 2019-05-29T19:23:12Z

deploy/deploy_ancillaryRH7.yml

+
+    - name: Extract repo to destination point
+      shell:  tar xvf /tmp/ancilRH7_repo.tar.gz -C /opt/ancillary_local
+    - name: Extract OpenOffice 4.1.6 


Shouldn't we use the existing open_office role for this?

@lel @stirlingv Yep, use existing roles when possible.

stirlingv · 2019-05-29T19:25:40Z

deploy/deploy_ancillaryRH7.dev_local

+    - sublime3
+#   - ultra-edit
+    - ultra-editRH7
+    - texliveRH7


@lel99999 Why are we calling these roles for the local install, but not the prod deployment? Looks like in prod we're deploying each role as a task in the playbook. I think we prefer to break them into roles.

Also, why are there two separate playbooks for local and prod - typically we've used the when: custom_repo tag to be a determination between prod and local development.

just a marker to work out the diffs and conditionals before a single playbook covering multiple scenarios are integrated

stirlingv · 2019-05-29T19:26:18Z

deploy/deploy_ancillaryRH7.dev_local

+    - texliveRH7
+
+  post_tasks:
+#   - name: Install texlive


@lel99999 probably want to remove commented out code throughout.

tanderegg

@lel99999 Left some comments in addition to @stirlingv's comments, can you review? Thanks!

tanderegg · 2019-06-03T18:25:45Z

deploy/Vagrantfile

@@ -352,6 +352,26 @@ Vagrant.configure(2) do |config|
    server.vm.network :private_network, ip: "10.0.1.18"
  end

+  # Research ancillary server1 on RedHat 7.5 and above
+  config.vm.define :research_ancillary1_services do |server|
+#   server.vm.box = "bento/centos-6.10"


@lel99999 Could you remove commented out lines? Also, to stick with previous conventions please call this config research_ancillary_services_7

tanderegg · 2019-06-03T18:26:38Z

deploy/Vagrantfile

+    server.ssh.forward_agent = true
+
+    server.vm.provision "ansible" do |ansible|
+      ansible.playbook = "deploy_ancillaryRH7.dev_local"


@lel99999 We should not have separate playbooks for local and production, the same playbooks should be used and controlled by variables that can be overwritten.

tanderegg · 2019-06-03T20:01:40Z

deploy/deploy_ancillaryRH7.yml

+  pre_tasks:
+    - debug:
+        msg: "Variables: _uid = {{ _uid }}, _pwd = **********"
+#       msg: "Variables: _uid = {{ _uid }}, _pwd = {{ _pwd }}"


@lel99999 Remove debug code

tanderegg · 2019-06-03T20:02:10Z

deploy/deploy_ancillaryRH7.yml

@@ -0,0 +1,142 @@
+- hosts: wdcreancil02
+  vars:  
+    custom_repo: true


@lel99999 We do not want to hard-code custom_repo to be true, it should only be true in remote environments.

tanderegg · 2019-06-03T20:03:11Z

deploy/deploy_ancillaryRH7.yml

+      shell: yum -y groupinstall "X Window System"
+
+    - name: install XFCE
+      shell: yum -y groupinstall "xfce"


@lel99999 I don't think we need to install xfce on the Ancillary, since the desktop lives on EOD and apps are connected to via X11 forwarding only.

tanderegg · 2019-06-03T20:03:29Z

deploy/deploy_ancillaryRH7.yml

+      shell: yum -y install evince
+
+    - name: Install python-pip
+      shell: yum install -y python27 python-pip


@lel99999 There's already a role for python, we should use that instead.

tanderegg · 2019-06-03T20:03:50Z

deploy/deploy_ancillaryRH7.yml

+#       name: python27-python-pip
+#       state: latest
+    - name: Install python 3.6 and pip
+      shell: yum install -y python36 python36-pip


@lel99999 Same here, there's a role for python3 that should be used.

tanderegg · 2019-06-03T20:04:13Z

deploy/deploy_ancillaryRH7.yml

+      shell: mkdir -p /opt/ancillary_local/OO416
+    - name: make Sublime3 directory
+      shell: mkdir -p /opt/ancillary_local/Sublime3
+    - name: make Sublime3 install directory


@lel99999 What are these folders for?

folders are for custom local repo to stage installation files like /artifacts, will update to use /artifacts instead

tanderegg · 2019-06-03T20:04:38Z

deploy/deploy_ancillaryRH7.yml

+
+    - name: Extract repo to destination point
+      shell:  tar xvf /tmp/ancilRH7_repo.tar.gz -C /opt/ancillary_local
+    - name: Extract OpenOffice 4.1.6 


@lel @stirlingv Yep, use existing roles when possible.

tanderegg · 2019-06-03T20:07:03Z

deploy/roles/stattransfer14/defaults/main.yaml

+stattransfer_major_version: "14"
+stattransfer_name: "STAT-TRANSFER-NAME"
+stattransfer_organization: "STAT-TRANSFER-ORGANIZATION"
+stattransfer_set_code: "STAT-TRANSFER-SET-CODE"


@lel99999 Ideally we won't have a new role for stattransfer14 vs 13, just update the existing role with the new variable values. That way we can control both versions using the same role while incrementally upgrading machines.

stirlingv · 2019-06-21T13:34:40Z

deploy/roles/ultra-editRH7/defaults/main.yml

+  - UltraEdit-15.1-0.8.x86_64
+
+ue_install_version: UltraEdit-18.0-0.40.el7.x86_64
+ue_install_rpm: UltraEdit-18.0-0.40.el7.x86_64.rpm


@lel99999 did you add this rpm to the SE repo for managed rpms? Typically we prefer to yum install that way, rather than from source ourselves.

stirlingv · 2019-06-21T13:35:42Z

deploy/roles/ultra-editRH7/tasks/main.yml

+    - UltraEdit
+
+- name: Install Ultra Edit
+  shell:  yum localinstall -y {{ ue_install_dir }}/{{ ue_install_rpm }}


@lel99999 see comment above. We want to send SE the RPM so that can add it to RH satellite.

stirlingv · 2019-06-21T13:46:21Z

deploy/deploy_ancillaryRH7.dev_local

+      shell: yum -y groupinstall "xfce"
+
+    - name: install Evince
+      shell: yum -y install evince


There is a whole role for this, that seems to require installing many more dependencies. I'm going to remove this and call the evince role.

stirlingv · 2019-06-21T14:20:07Z

deploy/deploy_ancillaryRH7.dev_local

+      shell: pip install gdown  
+#     yum:
+#       name: python27-python-pip
+#       state: latest


@lel99999 we should call the python27 role here.

lel99999 added 5 commits May 2, 2019 17:55

commit ancillary rhel7

49212e9

upd Vagrantfile vagrant_hosts

492e087

upd ancillary host info, open_officeRH7 role

1c85dcb

upd deploy, activate gdown

a2e74e4

add comment

7318e5b

stirlingv reviewed May 29, 2019

View reviewed changes

tanderegg requested changes Jun 3, 2019

View reviewed changes

stirlingv reviewed Jun 21, 2019

View reviewed changes

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Develop ancillaryrh7 #368

Develop ancillaryrh7 #368

lel99999 commented May 3, 2019

stirlingv May 29, 2019

stirlingv May 29, 2019

stirlingv May 29, 2019

stirlingv May 29, 2019

stirlingv May 29, 2019

stirlingv May 29, 2019

lel99999 Jun 3, 2019

stirlingv May 29, 2019

lel99999 Jun 3, 2019

stirlingv May 29, 2019

lel99999 Jun 3, 2019

stirlingv May 29, 2019

tanderegg Jun 3, 2019

stirlingv May 29, 2019

lel99999 Jun 3, 2019

stirlingv May 29, 2019

tanderegg left a comment

tanderegg Jun 3, 2019

tanderegg Jun 3, 2019

tanderegg Jun 3, 2019

tanderegg Jun 3, 2019

tanderegg Jun 3, 2019

tanderegg Jun 3, 2019

tanderegg Jun 3, 2019

tanderegg Jun 3, 2019

lel99999 Jun 3, 2019

tanderegg Jun 3, 2019

tanderegg Jun 3, 2019

stirlingv Jun 21, 2019

stirlingv Jun 21, 2019

stirlingv Jun 21, 2019

stirlingv Jun 21, 2019

Develop ancillaryrh7 #368

Are you sure you want to change the base?

Develop ancillaryrh7 #368

Conversation

lel99999 commented May 3, 2019

Require free developer subscription: https://developers.redhat.com/blog/2016/03/31/no-cost-rhel-developer-subscription-now-available/

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

tanderegg left a comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment