Ceo - Revision history

O32patel: fix Uploading Changes to Mirror

2026-01-22T03:58:49Z

fix Uploading Changes to Mirror

← Older revision		Revision as of 22:58, 21 January 2026
Line 101:		Line 101:

	Then you'll need to make a tar.gz file<syntaxhighlight lang="bash">		Then you'll need to make a tar.gz file<syntaxhighlight lang="bash">
	tar czf ~~ceo_1~~.0.31.orig.tar.gz pyceo/		tar czf ceo_<major>.<minor>.<patch>.orig.tar.gz pyceo/
	</syntaxhighlight>To build the package run debuild		</syntaxhighlight>To build the package run debuild

Line 107:		Line 107:

	This will generate the *.deb files in the parent directory.		This will generate the *.deb files in the parent directory.

			This may try to auto-sign with whatever your first GPG key is, you can safely exist and debsign yourself.

	=== Uploading Changes to Mirror ===		=== Uploading Changes to Mirror ===
	After you make the package, you'll need to sign it, this can be via debsign. (You can find the .changes file in the parent directory)<syntaxhighlight lang="bash">		After you make the package, you'll need to sign it, this can be via debsign. (You can find the .changes file in the parent directory)<syntaxhighlight lang="bash">
	debsign -k[GPG Key ID] [package].changes		debsign -k [GPG Key ID] [package].changes

	</syntaxhighlight>		</syntaxhighlight>

	In the directory containing the .deb and .changes files run		In the directory containing the .deb and .changes files run<syntaxhighlight lang="bash">
			dput -c /path/to/dput.cf ceo_<major>.<minor>.<patch>-<distribution>1_amd64.changes

			</syntaxhighlight>Here is a sample dput.cf<syntaxhighlight lang="ini">
	=== DO NOT USE DUPLOAD, THIS IS LEGACY DOCUMENTATION, USE `dput` INSTEAD. ASK SIRACHA FOR CONFIGS ===
			[DEFAULT]
	'''This needs to be done on high-fructose-corn-syrup because of the dupload configs'''
			default_host_main = debian.csclub
	dupload

			[debian.csclub]
⚫	Then ssh to mirror and run
			fqdn = potassium-benzoate.csclub.uwaterloo.ca
	sudo rrr-incoming
			method = scp
			incoming = /srv/debian/incoming
			run_install = 1
			pre_upload_command = /bin/true
			login = o32patel
		⚫	</syntaxhighlight>Then ssh to mirror and run
			reprepro --confdir /srv/debian/conf/ processincoming basic # use --ignore=longkeyid if you uploaded a long GPG id

	The package should now be uploaded and you can update in the usual way with apt-get/aptitude.		The package should now be uploaded and you can update in the usual way with apt-get/aptitude.

S23adhik at 18:58, 30 June 2025

2025-06-30T18:58:32Z

← Older revision		Revision as of 13:58, 30 June 2025
Line 125:		Line 125:
	The package should now be uploaded and you can update in the usual way with apt-get/aptitude.		The package should now be uploaded and you can update in the usual way with apt-get/aptitude.

			== How to deploy CEO ==
			Firstly, cry

			Secondly, check the usual place for all the passwords, install ceo. Install ceod if needed, and edit the configs to make sure the correct servers are contacted for the relevant services. Like install ceod on the management node of cloudstack.

			Then setup the kerberos tickets

			Then go to `/etc/csc`, and fill in all the ceo.ini, and ceod.ini configs
	[[Category:Software]]		[[Category:Software]]

S23adhik at 00:54, 12 June 2025

2025-06-12T00:54:54Z

← Older revision		Revision as of 19:54, 11 June 2025
Line 116:		Line 116:
	In the directory containing the .deb and .changes files run		In the directory containing the .deb and .changes files run

			=== DO NOT USE DUPLOAD, THIS IS LEGACY DOCUMENTATION, USE `dput` INSTEAD. ASK SIRACHA FOR CONFIGS ===
	'''This needs to be done on high-fructose-corn-syrup because of the dupload configs'''		'''This needs to be done on high-fructose-corn-syrup because of the dupload configs'''
	dupload		dupload

S23adhik at 23:09, 11 June 2025

2025-06-11T23:09:07Z

← Older revision		Revision as of 18:09, 11 June 2025
Line 115:		Line 115:

	In the directory containing the .deb and .changes files run		In the directory containing the .deb and .changes files run

			'''This needs to be done on high-fructose-corn-syrup because of the dupload configs'''
	dupload		dupload

S23adhik at 22:33, 11 June 2025

2025-06-11T22:33:01Z

← Older revision		Revision as of 17:33, 11 June 2025
Line 96:		Line 96:
	dch -i		dch -i

	Add a description of your change and then save and quit. Once you are sure of your changes commit them to the git repository and push them (test them first!). ~~To build the package run debuild~~		Add a description of your change and then save and quit. Once you are sure of your changes commit them to the git repository and push them (test them first!).

		⚫	Make sure to set a distribution, like distribution UNRELEASED is NOT allowed. So change it to whatever distribution you're deploying to in the <code>debian/changelog</code> file

			Then you'll need to make a tar.gz file<syntaxhighlight lang="bash">
			tar czf ceo_1.0.31.orig.tar.gz pyceo/
			</syntaxhighlight>To build the package run debuild

	debuild		debuild
Line 102:		Line 108:
	This will generate the *.deb files in the parent directory.		This will generate the *.deb files in the parent directory.

	=== ~~Siracha's~~ ~~Notes~~ ===		=== Uploading Changes to Mirror ===
⚫	Make sure to set a distribution, like distribution UNRELEASED is NOT allowed. So change it to whatever distribution you're deploying to in the <code>debian/changelog</code> file

	After you make the package, you'll need to sign it, this can be via debsign. (You can find the .changes file in the parent directory)<syntaxhighlight lang="bash">		After you make the package, you'll need to sign it, this can be via debsign. (You can find the .changes file in the parent directory)<syntaxhighlight lang="bash">
	debsign -k[GPG Key ID] [package].changes		debsign -k[GPG Key ID] [package].changes

	</syntaxhighlight>		</syntaxhighlight>

	=== Uploading Changes to Mirror ===

	In the directory containing the .deb and .changes files run		In the directory containing the .deb and .changes files run

S23adhik: Adding some info abt how to

2025-06-11T22:20:22Z

Adding some info abt how to

← Older revision		Revision as of 17:20, 11 June 2025
Line 101:		Line 101:

	This will generate the *.deb files in the parent directory.		This will generate the *.deb files in the parent directory.

			=== Siracha's Notes ===
			Make sure to set a distribution, like distribution UNRELEASED is NOT allowed. So change it to whatever distribution you're deploying to in the <code>debian/changelog</code> file

			After you make the package, you'll need to sign it, this can be via debsign. (You can find the .changes file in the parent directory)<syntaxhighlight lang="bash">
			debsign -k[GPG Key ID] [package].changes

			</syntaxhighlight>

	=== Uploading Changes to Mirror ===		=== Uploading Changes to Mirror ===

R389li: Redo member deletion and add membership change

2022-01-20T22:52:54Z

Redo member deletion and add membership change

← Older revision		Revision as of 17:52, 20 January 2022
Line 28:		Line 28:
	= raymo's guide on how to fix things after screwing up =		= raymo's guide on how to fix things after screwing up =

	== ~~Deleting~~ a member ==		== Changing a member to a nonmember (club rep) and vice-versa ==

⚫	* '''RULE: Never do this without good reason. We should NEVER delete accounts or groups that have been used before.'''

	Perhaps you created a club rep as a regular member instead (I ''totally'' didn't do this and then merenber gave me these commands). Perhaps it's for another reason that doesn't break the '''RULE''' above. No matter, don't panic, follow the following steps to erase a member account:

	ssh hfcs		ssh hfcs
	kinit # if you don't already have <u>[[Kerberos#raymo's guide to keytabs\|keytabs]]</u> set up		kinit # if you don't already have <u>[[Kerberos#raymo's guide to keytabs\|keytabs]]</u> set up
	ldapvi -Y GSSAPI		ldapvi -Y GSSAPI
	Use <code>/<username></code> to search for the user in vi and ~~delete~~ ~~both~~ ~~the~~ ~~user~~ ~~and~~ ~~group~~ ~~record.~~ ~~Records are separated by~~ ~~blank~~ ~~lines~~. When you're done deleting the file should no longer contain the username. Save and quit (<code>:wq</code>) and press <code>y</code> when prompted.		Use <code>/<username></code> to search for the user in vi and change <code>term</code> to <code>nonMemberTerm</code> (or vice-versa) for the relevant terms. When you're done deleting the file should no longer contain the username. Save and quit (<code>:wq</code>) and press <code>y</code> when prompted.

			== Deleting a member ==

		⚫	* '''RULE: Never do this without good reason. We should NEVER delete accounts or groups that have been used before.'''

			If you accidentally created a club rep as a regular member instead, see the [previous section\|Ceo#Changing a member to a nonmember (club rep) and vice-versa]. For another reason that doesn't break the '''RULE''' above, first follow the steps in the change membership section above, up to and including <code>ldapvi</code>, then delete both the user and group LDAP records. These are separated by blank lines. When you're done deleting the file should no longer contain the username. Save and quit as if changing membership. Then:
	ssh auth1		ssh auth1
	sudo kadmin.local		sudo kadmin.local
Line 43:		Line 45:
	ssh phosphoric acid		ssh phosphoric acid
	sudo rm -rfI /users/<username>		sudo rm -rfI /users/<username>
	* Unsubscribe the user from [https://mailman.csclub.uwaterloo.ca/postorius/lists/syscom.csclub.uwaterloo.ca/members/member/ csc-general on mailman]		Unsubscribe the user from [https://mailman.csclub.uwaterloo.ca/postorius/lists/syscom.csclub.uwaterloo.ca/members/member/ csc-general on mailman]

	= Feature Requests and Ideas =		= Feature Requests and Ideas =

R389li: /* Deleting a member */ Fix formatting

2022-01-19T03:39:56Z

Deleting a member: Fix formatting

← Older revision		Revision as of 22:39, 18 January 2022
Line 34:		Line 34:
	Perhaps you created a club rep as a regular member instead (I ''totally'' didn't do this and then merenber gave me these commands). Perhaps it's for another reason that doesn't break the '''RULE''' above. No matter, don't panic, follow the following steps to erase a member account:		Perhaps you created a club rep as a regular member instead (I ''totally'' didn't do this and then merenber gave me these commands). Perhaps it's for another reason that doesn't break the '''RULE''' above. No matter, don't panic, follow the following steps to erase a member account:

	* <pre>ssh hfcs~~</pre>~~		ssh hfcs
			kinit # if you don't already have <u>[[Kerberos#raymo's guide to keytabs\|keytabs]]</u> set up
	* <pre>kinit</pre>
	* <pre>ldapvi -Y GSSAPI~~</pre>~~		ldapvi -Y GSSAPI
	* Use <code>/<username></code> to search for the user in vi and delete both the user and group record. Records are separated by blank lines. When you're done deleting the file should no longer contain the username. Save and quit (<code>:wq</code>) and press <code>y</code> when prompted.		Use <code>/<username></code> to search for the user in vi and delete both the user and group record. Records are separated by blank lines. When you're done deleting the file should no longer contain the username. Save and quit (<code>:wq</code>) and press <code>y</code> when prompted.
	* <pre>ssh auth1~~</pre>~~		ssh auth1
	* <pre>sudo kadmin.local~~</pre>~~		sudo kadmin.local
	* <pre>delprinc <username~~></pre~~>		delprinc <username>
	* <pre>ssh phosphoric acid~~</pre>~~		ssh phosphoric acid
	* <pre>sudo rm -rfI /users/<username~~></pre~~>		sudo rm -rfI /users/<username>
	* Unsubscribe the user from [https://mailman.csclub.uwaterloo.ca/postorius/lists/syscom.csclub.uwaterloo.ca/members/member/ csc-general on mailman]		* Unsubscribe the user from [https://mailman.csclub.uwaterloo.ca/postorius/lists/syscom.csclub.uwaterloo.ca/members/member/ csc-general on mailman]

R389li: Fix link

2022-01-02T21:08:23Z

Fix link

← Older revision		Revision as of 16:08, 2 January 2022
Line 1:		Line 1:
	[[Image:Pyceo.png\|thumb\|300px\|right\|<tt>pyceo</tt>'s main menu screen]]		[[Image:Pyceo.png\|thumb\|300px\|right\|<tt>pyceo</tt>'s main menu screen]]

	ceo is the CSC member creation and administration interface. It was originally written in perl by persons of mysterious-ness, was re-written in python by Michael Spang in early 2007, and re-written again (in Python) by Syscom in 2020-2021. The source-code for ceo can be found in git: [~~http~~://git.csclub.uwaterloo.ca/~~?p=~~public/pyceo~~.git;a=summary~~ ~~csclub~~:/~~users~~/git/public/pyceo~~.git~~].		ceo is the CSC member creation and administration interface. It was originally written in perl by persons of mysterious-ness, was re-written in python by Michael Spang in early 2007, and re-written again (in Python) by Syscom in 2020-2021. The source-code for ceo can be found in git: [https://git.csclub.uwaterloo.ca/public/pyceo https://git.csclub.uwaterloo.ca/public/pyceo].

	= Instructions/Usage =		= Instructions/Usage =

R389li: Update to pyceo

2022-01-02T21:05:07Z

Update to pyceo

← Older revision		Revision as of 16:05, 2 January 2022
Line 1:		Line 1:
	[[Image:~~Ceo~~.png\|thumb\|300px\|right\|<tt>~~ceo~~</tt>'s main menu screen]]		[[Image:Pyceo.png\|thumb\|300px\|right\|<tt>pyceo</tt>'s main menu screen]]

	ceo is the CSC member creation and administration interface. It was originally written in perl by persons of mysterious-ness, ~~and~~ was re-written in python by Michael Spang in early 2007. The source-code for ceo can be found in git: [http://git.csclub.uwaterloo.ca/?p=public/pyceo.git;a=summary csclub:/users/git/public/pyceo.git].		ceo is the CSC member creation and administration interface. It was originally written in perl by persons of mysterious-ness, was re-written in python by Michael Spang in early 2007, and re-written again (in Python) by Syscom in 2020-2021. The source-code for ceo can be found in git: [http://git.csclub.uwaterloo.ca/?p=public/pyceo.git;a=summary csclub:/users/git/public/pyceo.git].

	= Instructions/Usage =		= Instructions/Usage =