Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Action to Generate Additional Domino Server ID #124

Open
JoelProminic opened this issue Dec 3, 2024 · 0 comments
Open

Action to Generate Additional Domino Server ID #124

JoelProminic opened this issue Dec 3, 2024 · 0 comments
Assignees
Labels
enhancement New feature or request
Milestone

Comments

@JoelProminic
Copy link
Contributor

JoelProminic commented Dec 3, 2024

From @JustinProminic

14:14:08: ok. and have you and Mark gotten the instructions and command line script for registering a new server and registering a new user ID, so we can use SHI to create first server in first domain, then the CLI tools to register aditional user/server, then download the ID back to the host, then use SHI to create on the same machine the second server to join the existing server? for SHI I think that is what we should target next to have that done.
14:28:47: doing what I just described - making it available for people to test creating fresh domains and adding additional fresh servers to the fresh domain -- remains a key undelivered goal of SHI that we need to close the gap on. this would allow for a lot of testing that we just cannot do right now without getting these steps fully done.

This is is a key part of the additional Domino server support (#85). This will be based on the CreateAdditionalServerID class that was added to the provisioners here (pending testing).

The current process is:
0. Requires a local standalone or additional Domino instance for the same Domino organization

  1. Create or deploy additional.properties in the instance
  2. SSH to the instance and navigate to the above directory as java_user
  3. Run java -jar CreateAdditionalServerID.jar additional.properties
  4. SCP the generated ID file to the local machine
  5. Create a new additional server instance and provide the generated ID file

UPDATE: Here are the commands I used in a real test (not including creating the additional server

vagrant ssh
sudo su - java_user
bash
mkdir /tmp/additional

# Create  /tmp/additional/additional.properties
server.name=test-additional.shi.com
server.id.password=password
server.id.title=test-additional.shi.com
server.id.output=/tmp/additional/test-additional.shi.com.id

java -jar /local/notesjava/CreateAdditionalServerID.jar /tmp/additional/additional.properties

With this configuration (server.id.output), the generated ID file is found at: /tmp/additional/test-additional.shi.com.id

The proposed process would be something like this:

  1. Select a local instance that shares the desired organization. Note that this must be using the updated provisiones
  2. Click Create Additional Server
  3. Fill in a form. Some information should be populated from the original server
  4. Generate the ID
    1. Generate CrossCertifyNotesID.proeprties based on the form input
    2. Deploy CrossCertifyNotesID.proeprties to the instance
    3. Run CreateAdditionalServerID.jar with the properties file
    4. Pull the ID file back to a temporary location on the local host
  5. Open the form to create a new Additional Domino instance and populate it with the entered information

TODO:

  • Finish testing the provisioner updates
  • Release 0.1.23 provisioner with the CreateAdditionalServerID logic. We can test these provisioners manually in the meantime
  • Make the instructions above more explicit (paths, format for JSON file)
@JoelProminic JoelProminic added the enhancement New feature or request label Dec 3, 2024
@JoelProminic JoelProminic added this to the v0.11.0 milestone Dec 3, 2024
piotrzarzycki21 added a commit that referenced this issue Dec 18, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

2 participants