Thread: Kusu use cases

Use case 1. How to add a os kit, and then assign it to a repository and then a node group?

Instance:

1. Add a kit by the following kitops command:
kitops -a -m /jkstart/iso/CentOS/5.2/x86_64-DVD/CentOS-5.2-x86_64-bin-DVD.iso

2. Create a new repo by the following repoman command:
repoman -n -r "TestRepo"

3. Add a kit to a repo by the following repoman command:
repoman -r "TestRepo" -a -k CentOS -o 5.2 -c x86_64

4. Refresh the repo by the following repoman command:
repoman -r "TestRepo" -u

5. Associate the new repo to a node group
Run ngedit and edit the node group's repo with the new repo.

Use case 2: How to change node group definition?

Run ngedit and select the compute-rhel-5-x86_64 definition to edit.

Use case 3: How to assign hosts to node groups?

Run nghosts and select the move selected nodes to a node group to move.

[BTW: The node can be moved successfully from package, imaged and diskless node group to any node group. But the node in installer group just can be moved to the same type group.]

Use case 4: How to synchronize packages and files for node groups?

The administrator calls ‘cfmsync –p –f -u’ to synchronize everything.

BTW: The cfmsync signals each node to spawn a cfmclient with appropriate arguments to retrieve files from the installer node, every cfmclient retrieves packages in package.lst files from the installer node – changed files get updated automatically and securely.

Use case 5: How to update the configuration files on nodegroup compute-diskless-test?

The administrator calls ‘cfmsync -f -n compute-diskless-test ’ to update the configuration files on nodegroup compute-diskless-test.

[BWT: If want to update a specific package by the command, how to do it?
Answer: cfmsync lets you do -p for package update,
this will update all packages from the repo in the compute,
you cant 'update' a speicfic package,
for that you can pdsh into the node and run yum update,
once you patch a repo,
you can then associate the nodegroup with this patched repo,
and then you run cfmsync -p,
this will sync the nodes.]

Use case 6: How to update the packages/components installed on nodegroup compute-diskless-test?

The administrator calls ‘cfmsync -p -n compute-diskless-test’ to update the packages/components installed on nodegroup compute-diskless-test.

Use case 7: How to patch the repository?

Patch a repo by the following command:
repopatch –r “TestRepo”

[BWT: The “TestRepo” can be patched with the latest OS vendors packages as described in its description, but how to insert the update packages to kusu system? How to realize the update packages in kusu?
Answer: the repopatch will provide an updated kit,
u can add the kit to a repository using repoman]


Use case 8: How to query kusu database

Instance:
Query kusu datebase by the following sqlrunner command:
sqlrunner -q "select * from Repos"

Use case 9: How to create a new network definition?

Run netedit and select new to create a new network definition.

Use case 10: To generate a new root filesystem for the default diskless nodegroup using Red Hat 5 run:

buildimage -n compute-diskless-rhel-5-x86_64

[BTW:Buildimage performs the following steps:
Creates a chrooted filesystem
creates a yum config and runs yum with the custom config.
Installs the packages into the chrooted filesystem
automatically installs the necessary Platform OCS 5 components.
cleans up the temporary yum cache.
tars and compresses the filesystem to create a root image.
]

Use case 11: To generate a new initrd for the default diskless nodegroup using Red Hat 5 run:

buildinitrd -n compute-diskless-rhel-5-x86_64

[BTW: The tool will take a template initrd and patch in the kernel modules listed in the Modules section listed in the Nodegroup Editor. The resulting initrd will be copied to the /tftpboot/kusu directory for use by the Diskless and Imaged nodes.]