ansible: add loongson-clfs-loongarch64-{1,2,3} (#3740)

[shipujin]

ansible: add loongson-clfs-loongarch64-{1,2,3} (#3740)

Refs: #3740

[mhdawson]

This looks reasonable to me, @richardlau could you take a look as well?

[shipujin]

In order to facilitate the management of the machine network, the network IP is adjusted, thank you

Best regards

[mhdawson]

@shipujin I tried to ssh into the two new machines and it just seems to hang ?

[shipujin]

@shipujin I tried to ssh into the two new machines and it just seems to hang ?

Sorry, I re-updated the port, please try again, thank you

Best regards

[mhdawson]

@shipujin thanks, I can log in with the updated ports.

@shipujin I assume that it will appear that connections from the machines will all come from the same ip, if so I don't think any additions will be needed to the firewall rules.

I'll try to look at adding them to Jenkins tomorrow.

[shipujin]

@shipujin thanks, I can log in with the updated ports.

ok

@shipujin I assume that it will appear that connections from the machines will all come from the same ip, if so I don't think any additions will be needed to the firewall rules.

Yes, now that the firewall content has been removed, there are no whitelist rules

I'll try to look at adding them to Jenkins tomorrow.

Okay, thank you for your help. Thank you

Best regards

[mhdawson]

@shipujin have you run the ansible playbooks on the new hosts? I went to see if

./systemd/system/jenkins.service

existed so that I could create the host in jenkins and add the secret to that file, but it does not seem to be there on the 2nd machine when I logged in. I think that should have been created with the ansible scripts but not populated with the secret.

[mhdawson]

It's likelyl we manually installed the jenkins service on the first machine, but we should have ansible configuring as much as possible as we roll out newer machines so hoping the PR to add the ansible configration would be covering that.

[shipujin]

existed so that I could create the host in jenkins and add the secret to that file, but it does not seem to be there on the 2nd machine when I logged in. I think that should have been created with the ansible scripts but not populated with the secret.

I am studying nodejs/build project today, I don't know how the new machine generates "secret", I may have to continue to study nodejs/build project

Best regards

[shipujin]

Resolve conflicting files

[shipujin]

It's likelyl we manually installed the jenkins service on the first machine, but we should have ansible configuring as much as possible as we roll out newer machines so hoping the PR to add the ansible configration would be covering that.

I am studying nodejs/build project today, I don't know how the new machine generates "secret", I may have to continue to study nodejs/build project.

Is it how to generate "secret", is it generated by which tool of the "nodejs/build" project, thx~

Best regards

[mhdawson]

It's ok if the ansible run does not install the right secret as that is not available until I create the machines in Jenkins. What I was hoping was that the ansible setup would create the ./systemd/system/jenkins.service. I could then ust update it once I create the machine with the right secret.

[shipujin]

What I was hoping was that the ansible setup would create the ./systemd/system/jenkins.service.

I added support for clfs-loongarch64 to the ansible/roles/jenkins-worker/vars/main.yml file, What command of ansible should I execute on the two new machines to verify my nodejs/build changes? Sorry, I don't know how to use 'ansible' on 'nodejs/build'

Best regards

diff --git a/ansible/roles/jenkins-worker/vars/main.yml b/ansible/roles/jenkins-worker/vars/main.yml                                                                                      
index 544c0ef..b5979b6 100644
--- a/ansible/roles/jenkins-worker/vars/main.yml
+++ b/ansible/roles/jenkins-worker/vars/main.yml
@@ -9,7 +9,7 @@ init: {
   freebsd: 'freebsd',
   ibmi: 'ibmi73',
   macos: 'macos',
-  systemd: ['centos7', 'debian', 'fedora', 'rhel7', 'rhel8', 'rhel9', 'ubuntu1604', 'ubuntu1804','ubuntu2204'],                                                                          
+  systemd: ['centos7', 'clfs', 'debian', 'fedora', 'rhel7', 'rhel8', 'rhel9', 'ubuntu1604', 'ubuntu1804','ubuntu2204'],                                                                  
   svc: 'smartos',
   zos_start: 'zos'
   }
@@ -61,6 +61,7 @@ jenkins: "{{ jenkins_init[init_type] }}"

 # some os'es needs different paths to java. add them here.
 java_path: {
+  'clfs': '/opt/jdk17/bin/java',
   'ibmi73': '/QOpenSys/pkgs/lib/jvm/openjdk-11/bin/java',
   'macos10.15': 'java',
   'macos11': 'java',

[mhdawson]

@shipujin these are the getting started instructions for using the Node.js ansible scripts - https://github.com/nodejs/build/tree/main/ansible#getting-started

[shipujin]

@shipujin these are the getting started instructions for using the Node.js ansible scripts - https://github.com/nodejs/build/tree/main/ansible#getting-started

Okay, I'm learning this

Best regards