Skip to content

Ticket Forge Modules / MODULES-2675 - Unique server_id #765

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

Closed
wants to merge 4 commits into from
Closed

Ticket Forge Modules / MODULES-2675 - Unique server_id #765

wants to merge 4 commits into from

Conversation

jkarns87
Copy link

@jkarns87 jkarns87 commented Oct 7, 2015

Ticket Forge Modules / MODULES-2675
Fixed Unique server_id facter fact. Allowing a unique id to be generated by reading in all 6 splits of the mac address, where as it was only reading in 4 of the 6 splits.

@DavidS
Copy link
Contributor

DavidS commented Oct 8, 2015

Hi @jmk61 , thanks for your contribution! Would you be son nice and squash this into a single commit, so as to keep the history clean?

See Squashing: https://git-scm.com/book/en/v2/Git-Tools-Rewriting-History#Squashing-Commits

@DavidS
Copy link
Contributor

DavidS commented Oct 8, 2015

A more difficult question: how is this fact used, and how will changing it's output impact the users of this?

@jkarns87
Copy link
Author

jkarns87 commented Oct 8, 2015

The fact is used to determine a unique server ID within the my.cnf which allows master-slave setups. By modifying the fact it will change the users server_id within their conf. It shouldn't have a direct effect on existing setups as I'm unware of a way to directly utilize this information within a setup other then distinguishing each mysql server in your setup.

Please let me know your thoughts, questions and concerns.

Thanks

Joseph Karns
System Administrator III
Penn State University
Outreach Information Technology
329 Innovation Blvd
Suite 306
State College, Pa 16803

----- Reply message -----
From: "David Schmitt" [email protected]
To: "puppetlabs/puppetlabs-mysql" [email protected]
Cc: "Joseph Karns" [email protected]
Subject: [puppetlabs-mysql] Ticket Forge Modules / MODULES-2675 - Unique server_id (#765)
Date: Thu, Oct 8, 2015 5:29 AM

A more difficult question: how is this fact used, and how will changing it's output impact the users of this?


Reply to this email directly or view it on GitHub:
#765 (comment)

The fact is used to determine a unique server ID within the my.cnf which allows master-slave setups. By modifying the fact it will change the users server_id within their conf. It shouldn't have a direct effect on existing setups as I'm unware of a way to directly utilize this information within a setup other then distinguishing each mysql server in your setup.

Please let me know your thoughts, questions and concerns.

Thanks

Joseph Karns
System Administrator III
Penn State University
Outreach Information Technology
329 Innovation Blvd
Suite 306
State College, Pa 16803

----- Reply message -----
From: "David Schmitt" [email protected]
To: "puppetlabs/puppetlabs-mysql" [email protected]
Cc: "Joseph Karns" [email protected]
Subject: [puppetlabs-mysql] Ticket Forge Modules / MODULES-2675 - Unique server_id (#765)
Date: Thu, Oct 8, 2015 5:29 AM

Joseph Karns added 2 commits October 8, 2015 22:20
…ate the unique id.

Also set the correct value of the unique id based off the macaddress in the spec test.
…k61/puppetlabs-mysql into ticket/MODULES-2675_server_id

* 'ticket/MODULES-2675_server_id' of https://github.com/jmk61/puppetlabs-mysql:
  Fixed server_id Spec Test with correct value
  Setting Total to 6. This allows all six splits of the mac address to be used in calculating the unique id.
@jkarns87
Copy link
Author

jkarns87 commented Oct 9, 2015

David:

Not sure if I did the squash correct. If not request the pull request and I'll resubmit.

Thanks
Joey

@DavidS
Copy link
Contributor

DavidS commented Oct 9, 2015

Yeah, this branch doesn't look like it should. Also, I'm still not 100% clear what happens to an existing replication setup, when all the server_ids change. The docs don't seem to address that.

@DavidS
Copy link
Contributor

DavidS commented Oct 14, 2015

Closing in preference to #767

@DavidS DavidS closed this Oct 14, 2015
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants