User:Lucas/Gentoo Install Notes - Revision history

Lucas at 13:10, 23 February 2014

2014-02-23T13:10:52Z

← Older revision		Revision as of 15:10, 23 February 2014
Line 14:		Line 14:
	* install librarian: <code>gem19 install librarian-puppet</code>		* install librarian: <code>gem19 install librarian-puppet</code>
	* load puppet modules: <code>cd /etc/puppet/environments/development && librarian-puppet install</code>		* load puppet modules: <code>cd /etc/puppet/environments/development && librarian-puppet install</code>
	* workaround some TODOs: <code>ln -s /etc/puppet/environments/development/ /vagrant ~~&& mkdir /usr/local/portage && touch /usr/local/portage/make.conf~~ && ulimit -n 2048 ~~&& emerge sudo~~ && emerge dev-ruby/rgen --autounmask-write && dispatch-conf && emerge dev-ruby/rgen</code>		* workaround some TODOs: <code>ln -s /etc/puppet/environments/development/ /vagrant && ulimit -n 2048 && emerge dev-ruby/rgen --autounmask-write && dispatch-conf && emerge dev-ruby/rgen</code>
	* test if puppet is useable: <code>puppet apply --environment=development --modulepath=/etc/puppet/environments/development/modules/:/etc/puppet/environments/development/manifests/ -e 'notify{"test":}' --pluginsync</code>		* test if puppet is useable: <code>puppet apply --environment=development --modulepath=/etc/puppet/environments/development/modules/:/etc/puppet/environments/development/manifests/ -e 'notify{"test":}' --pluginsync</code>
	* run puppet like so to find the first batch of stuff to fix: <code>puppet apply --environment=development --modulepath=/etc/puppet/environments/development/modules/:/etc/puppet/environments/development/manifests/ -e 'include ::role::puppet::master' --pluginsync --noop</code>		* run puppet like so to find the first batch of stuff to fix: <code>puppet apply --environment=development --modulepath=/etc/puppet/environments/development/modules/:/etc/puppet/environments/development/manifests/ -e 'include ::role::puppet::master' --pluginsync --noop</code>
Line 29:		Line 29:

	== TODOs ==		== TODOs ==
	* replace silly headers in orcatamer with block chars with something that most tools dont bork on (ie. some ascii art)
	** I removed this on Puppetfile and Modulefile to get librarian to run
	* use github https URLs through out, they are simply proxy friendlier everywhere
	* refactor role and profile things into proper modules and use proper puppet:// data urls		* refactor role and profile things into proper modules and use proper puppet:// data urls
	* dont' depend on /usr/local/portage/make.conf
	* figure out why the betagarden overlay needs <code>ulimit -n 2048</code> to clone		* figure out why the betagarden overlay needs <code>ulimit -n 2048</code> to clone
	* figure out why layman-add from betagarden needs sudo
	* install rgen for puppet parser future at some sensible part of bootstrapping		* install rgen for puppet parser future at some sensible part of bootstrapping
	* figure out what going on here: <code>Feb 22 22:30:01 vm-test-01 ulogd[30493]: p_kvm-0231_0_in Denied dst:: IN=vmbr0 OUT=vmbr0 MAC=01:00:5e:00:00:12:00:00:5e:00:01:03:08:00 SRC=192.168.140.2 DST=224.0.0.18 LEN=56 TOS=10 PREC=0x00 TTL=255 ID=33458 DF PROTO=112 MARK=0 </code>		* figure out what going on here: <code>Feb 22 22:30:01 vm-test-01 ulogd[30493]: p_kvm-0231_0_in Denied dst:: IN=vmbr0 OUT=vmbr0 MAC=01:00:5e:00:00:12:00:00:5e:00:01:03:08:00 SRC=192.168.140.2 DST=224.0.0.18 LEN=56 TOS=10 PREC=0x00 TTL=255 ID=33458 DF PROTO=112 MARK=0 </code>
			* get rid of <code>/vargant</code> hard-deps.
			* make git with USE="curl"

Lucas at 12:07, 23 February 2014

2014-02-23T12:07:35Z

← Older revision		Revision as of 14:07, 23 February 2014
Line 26:		Line 26:
	* open ldap port in fw: <code>ldap_pub_out="10.1.130.13"</code> and <code>openTcpPortOut "${chains_out[pub]}" "$ldap_pub_out" "636"</code>		* open ldap port in fw: <code>ldap_pub_out="10.1.130.13"</code> and <code>openTcpPortOut "${chains_out[pub]}" "$ldap_pub_out" "636"</code>
	** i also need to configure <code>ldaps_int_in="${ip_int[vm-test-02]} ${ip_int[vm-test-03]} 192.168.140.136"</code> in <code>/usr/local/scripts/netfilter/local/chains/vm-test-01/vm-test-01_chain.sh</code> for the above to work.		** i also need to configure <code>ldaps_int_in="${ip_int[vm-test-02]} ${ip_int[vm-test-03]} 192.168.140.136"</code> in <code>/usr/local/scripts/netfilter/local/chains/vm-test-01/vm-test-01_chain.sh</code> for the above to work.
			** after all the above i can still not connect from my node to the ldap server. I'll have ot get the iptables gurus on board to solve this. We need more documentation on the setup if a as simple dev should be able to change this. At some point I might even consider puppetizing th eiptables config.

	== TODOs ==		== TODOs ==

Lucas at 21:49, 22 February 2014

2014-02-22T21:49:03Z

← Older revision		Revision as of 23:49, 22 February 2014
Line 24:		Line 24:
	* setup openldap tooling: emerge openldap		* setup openldap tooling: emerge openldap
	* search for machine: <code>ldapsearch -D 'cn=Manager,dc=stoney-cloud,dc=org' -w admin '(&(objectClass=sstVirtualizationVirtualMachine)(sstNetworkHostname=kvm-0231))'</code>		* search for machine: <code>ldapsearch -D 'cn=Manager,dc=stoney-cloud,dc=org' -w admin '(&(objectClass=sstVirtualizationVirtualMachine)(sstNetworkHostname=kvm-0231))'</code>
			* open ldap port in fw: <code>ldap_pub_out="10.1.130.13"</code> and <code>openTcpPortOut "${chains_out[pub]}" "$ldap_pub_out" "636"</code>
			** i also need to configure <code>ldaps_int_in="${ip_int[vm-test-02]} ${ip_int[vm-test-03]} 192.168.140.136"</code> in <code>/usr/local/scripts/netfilter/local/chains/vm-test-01/vm-test-01_chain.sh</code> for the above to work.

	== TODOs ==		== TODOs ==

Lucas at 21:31, 22 February 2014

2014-02-22T21:31:15Z

← Older revision		Revision as of 23:31, 22 February 2014
Line 20:		Line 20:
	* after running the last command until all the errors where fixed i can try to run in agent mode: <code>puppet agent --test --server=`hostname -f`</code>		* after running the last command until all the errors where fixed i can try to run in agent mode: <code>puppet agent --test --server=`hostname -f`</code>
	** i still need to figure out why the <code>--server</code> flag is needed at this stage, somehow the agent is consulting DNS rather than <code>/etc/hosts</code>		** i still need to figure out why the <code>--server</code> flag is needed at this stage, somehow the agent is consulting DNS rather than <code>/etc/hosts</code>

			now for some hacking that i did to test some concepts:
			* setup openldap tooling: emerge openldap
			* search for machine: <code>ldapsearch -D 'cn=Manager,dc=stoney-cloud,dc=org' -w admin '(&(objectClass=sstVirtualizationVirtualMachine)(sstNetworkHostname=kvm-0231))'</code>

	== TODOs ==		== TODOs ==
Line 30:		Line 34:
	* figure out why layman-add from betagarden needs sudo		* figure out why layman-add from betagarden needs sudo
	* install rgen for puppet parser future at some sensible part of bootstrapping		* install rgen for puppet parser future at some sensible part of bootstrapping
			* figure out what going on here: <code>Feb 22 22:30:01 vm-test-01 ulogd[30493]: p_kvm-0231_0_in Denied dst:: IN=vmbr0 OUT=vmbr0 MAC=01:00:5e:00:00:12:00:00:5e:00:01:03:08:00 SRC=192.168.140.2 DST=224.0.0.18 LEN=56 TOS=10 PREC=0x00 TTL=255 ID=33458 DF PROTO=112 MARK=0 </code>

Lucas at 21:06, 22 February 2014

2014-02-22T21:06:07Z

← Older revision		Revision as of 23:06, 22 February 2014
Line 18:		Line 18:
	* run puppet like so to find the first batch of stuff to fix: <code>puppet apply --environment=development --modulepath=/etc/puppet/environments/development/modules/:/etc/puppet/environments/development/manifests/ -e 'include ::role::puppet::master' --pluginsync --noop</code>		* run puppet like so to find the first batch of stuff to fix: <code>puppet apply --environment=development --modulepath=/etc/puppet/environments/development/modules/:/etc/puppet/environments/development/manifests/ -e 'include ::role::puppet::master' --pluginsync --noop</code>
	* let puppet rip: <code>puppet apply --environment=development --modulepath=/etc/puppet/environments/development/modules/:/etc/puppet/environments/development/manifests/ -e 'include ::role::puppet::master' --pluginsync </code>		* let puppet rip: <code>puppet apply --environment=development --modulepath=/etc/puppet/environments/development/modules/:/etc/puppet/environments/development/manifests/ -e 'include ::role::puppet::master' --pluginsync </code>
	* after running the last command until all the errors where fixed i can try to run in agent mode: <code>puppet agent --test --~~noop~~</code>		* after running the last command until all the errors where fixed i can try to run in agent mode: <code>puppet agent --test --server=`hostname -f`</code>
			** i still need to figure out why the <code>--server</code> flag is needed at this stage, somehow the agent is consulting DNS rather than <code>/etc/hosts</code>

	== TODOs ==		== TODOs ==

Lucas at 18:37, 22 February 2014

2014-02-22T18:37:21Z

← Older revision		Revision as of 20:37, 22 February 2014
Line 18:		Line 18:
	* run puppet like so to find the first batch of stuff to fix: <code>puppet apply --environment=development --modulepath=/etc/puppet/environments/development/modules/:/etc/puppet/environments/development/manifests/ -e 'include ::role::puppet::master' --pluginsync --noop</code>		* run puppet like so to find the first batch of stuff to fix: <code>puppet apply --environment=development --modulepath=/etc/puppet/environments/development/modules/:/etc/puppet/environments/development/manifests/ -e 'include ::role::puppet::master' --pluginsync --noop</code>
	* let puppet rip: <code>puppet apply --environment=development --modulepath=/etc/puppet/environments/development/modules/:/etc/puppet/environments/development/manifests/ -e 'include ::role::puppet::master' --pluginsync </code>		* let puppet rip: <code>puppet apply --environment=development --modulepath=/etc/puppet/environments/development/modules/:/etc/puppet/environments/development/manifests/ -e 'include ::role::puppet::master' --pluginsync </code>
			* after running the last command until all the errors where fixed i can try to run in agent mode: <code>puppet agent --test --noop</code>

	== TODOs ==		== TODOs ==

Lucas at 18:16, 22 February 2014

2014-02-22T18:16:37Z

← Older revision		Revision as of 20:16, 22 February 2014
Line 16:		Line 16:
	* workaround some TODOs: <code>ln -s /etc/puppet/environments/development/ /vagrant && mkdir /usr/local/portage && touch /usr/local/portage/make.conf && ulimit -n 2048 && emerge sudo && emerge dev-ruby/rgen --autounmask-write && dispatch-conf && emerge dev-ruby/rgen</code>		* workaround some TODOs: <code>ln -s /etc/puppet/environments/development/ /vagrant && mkdir /usr/local/portage && touch /usr/local/portage/make.conf && ulimit -n 2048 && emerge sudo && emerge dev-ruby/rgen --autounmask-write && dispatch-conf && emerge dev-ruby/rgen</code>
	* test if puppet is useable: <code>puppet apply --environment=development --modulepath=/etc/puppet/environments/development/modules/:/etc/puppet/environments/development/manifests/ -e 'notify{"test":}' --pluginsync</code>		* test if puppet is useable: <code>puppet apply --environment=development --modulepath=/etc/puppet/environments/development/modules/:/etc/puppet/environments/development/manifests/ -e 'notify{"test":}' --pluginsync</code>
	* run puppet like so to find the first batch of stuff to fix: <code>puppet apply --environment=development --modulepath=/etc/puppet/environments/development/modules/:/etc/puppet/environments/~~developmen~~		* run puppet like so to find the first batch of stuff to fix: <code>puppet apply --environment=development --modulepath=/etc/puppet/environments/development/modules/:/etc/puppet/environments/development/manifests/ -e 'include ::role::puppet::master' --pluginsync --noop</code>
	t/manifests/ -e 'include ::role::puppet::master' --pluginsync --noop</code>		* let puppet rip: <code>puppet apply --environment=development --modulepath=/etc/puppet/environments/development/modules/:/etc/puppet/environments/development/manifests/ -e 'include ::role::puppet::master' --pluginsync </code>
	* let puppet rip: <code>puppet apply --environment=development --modulepath=/etc/puppet/environments/development/modules/:/etc/puppet/environments/~~developmen~~
	t/manifests/ -e 'include ::role::puppet::master' --pluginsync </code>

	== TODOs ==		== TODOs ==

Lucas at 18:09, 22 February 2014

2014-02-22T18:09:24Z

← Older revision		Revision as of 20:09, 22 February 2014
Line 14:		Line 14:
	* install librarian: <code>gem19 install librarian-puppet</code>		* install librarian: <code>gem19 install librarian-puppet</code>
	* load puppet modules: <code>cd /etc/puppet/environments/development && librarian-puppet install</code>		* load puppet modules: <code>cd /etc/puppet/environments/development && librarian-puppet install</code>
	* workaround some TODOs: <code>ln -s /etc/puppet/environments/development/ /vagrant && mkdir /usr/local/portage && touch /usr/local/portage/make.conf && ulimit -n 2048 && emerge sudo</code>		* workaround some TODOs: <code>ln -s /etc/puppet/environments/development/ /vagrant && mkdir /usr/local/portage && touch /usr/local/portage/make.conf && ulimit -n 2048 && emerge sudo && emerge dev-ruby/rgen --autounmask-write && dispatch-conf && emerge dev-ruby/rgen</code>
	* test if puppet is useable: <code>puppet apply --environment=development --modulepath=/etc/puppet/environments/development/modules/:/etc/puppet/environments/development/manifests/ -e 'notify{"test":}' --pluginsync</code>		* test if puppet is useable: <code>puppet apply --environment=development --modulepath=/etc/puppet/environments/development/modules/:/etc/puppet/environments/development/manifests/ -e 'notify{"test":}' --pluginsync</code>
	* run puppet like so to find the first batch of stuff to fix: <code>puppet apply --environment=development --modulepath=/etc/puppet/environments/development/modules/:/etc/puppet/environments/developmen		* run puppet like so to find the first batch of stuff to fix: <code>puppet apply --environment=development --modulepath=/etc/puppet/environments/development/modules/:/etc/puppet/environments/developmen
Line 29:		Line 29:
	* figure out why the betagarden overlay needs <code>ulimit -n 2048</code> to clone		* figure out why the betagarden overlay needs <code>ulimit -n 2048</code> to clone
	* figure out why layman-add from betagarden needs sudo		* figure out why layman-add from betagarden needs sudo
			* install rgen for puppet parser future at some sensible part of bootstrapping

Lucas at 18:07, 22 February 2014

2014-02-22T18:07:30Z

← Older revision		Revision as of 20:07, 22 February 2014
Line 14:		Line 14:
	* install librarian: <code>gem19 install librarian-puppet</code>		* install librarian: <code>gem19 install librarian-puppet</code>
	* load puppet modules: <code>cd /etc/puppet/environments/development && librarian-puppet install</code>		* load puppet modules: <code>cd /etc/puppet/environments/development && librarian-puppet install</code>
	* workaround some TODOs: <code>ln -s /etc/puppet/environments/development/ /vagrant && mkdir /usr/local/portage && touch /usr/local/portage/make.conf && ulimit -n 2048</code>		* workaround some TODOs: <code>ln -s /etc/puppet/environments/development/ /vagrant && mkdir /usr/local/portage && touch /usr/local/portage/make.conf && ulimit -n 2048 && emerge sudo</code>
	* test if puppet is useable: <code>puppet apply --environment=development --modulepath=/etc/puppet/environments/development/modules/:/etc/puppet/environments/development/manifests/ -e 'notify{"test":}' --pluginsync</code>		* test if puppet is useable: <code>puppet apply --environment=development --modulepath=/etc/puppet/environments/development/modules/:/etc/puppet/environments/development/manifests/ -e 'notify{"test":}' --pluginsync</code>
	* run puppet like so to find the first batch of stuff to fix: <code>puppet apply --environment=development --modulepath=/etc/puppet/environments/development/modules/:/etc/puppet/environments/developmen		* run puppet like so to find the first batch of stuff to fix: <code>puppet apply --environment=development --modulepath=/etc/puppet/environments/development/modules/:/etc/puppet/environments/developmen
Line 27:		Line 27:
	* refactor role and profile things into proper modules and use proper puppet:// data urls		* refactor role and profile things into proper modules and use proper puppet:// data urls
	* dont' depend on /usr/local/portage/make.conf		* dont' depend on /usr/local/portage/make.conf
	* figure out why the betagarden overlay needs <code>ulimit -n 2048</~~clone~~> to clone		* figure out why the betagarden overlay needs <code>ulimit -n 2048</code> to clone
			* figure out why layman-add from betagarden needs sudo

Lucas at 18:05, 22 February 2014

2014-02-22T18:05:18Z

← Older revision		Revision as of 20:05, 22 February 2014
Line 14:		Line 14:
	* install librarian: <code>gem19 install librarian-puppet</code>		* install librarian: <code>gem19 install librarian-puppet</code>
	* load puppet modules: <code>cd /etc/puppet/environments/development && librarian-puppet install</code>		* load puppet modules: <code>cd /etc/puppet/environments/development && librarian-puppet install</code>
	* workaround some TODOs: <code>ln -s /etc/puppet/environments/development/ /vagrant && mkdir /usr/local/portage && touch /usr/local/portage/make.conf</code>		* workaround some TODOs: <code>ln -s /etc/puppet/environments/development/ /vagrant && mkdir /usr/local/portage && touch /usr/local/portage/make.conf && ulimit -n 2048</code>
	* test if puppet is useable: <code>puppet apply --environment=development --modulepath=/etc/puppet/environments/development/modules/:/etc/puppet/environments/development/manifests/ -e 'notify{"test":}' --pluginsync</code>		* test if puppet is useable: <code>puppet apply --environment=development --modulepath=/etc/puppet/environments/development/modules/:/etc/puppet/environments/development/manifests/ -e 'notify{"test":}' --pluginsync</code>
	* run puppet like so to find the first batch of stuff to fix: <code>puppet apply --environment=development --modulepath=/etc/puppet/environments/development/modules/:/etc/puppet/environments/developmen		* run puppet like so to find the first batch of stuff to fix: <code>puppet apply --environment=development --modulepath=/etc/puppet/environments/development/modules/:/etc/puppet/environments/developmen
Line 27:		Line 27:
	* refactor role and profile things into proper modules and use proper puppet:// data urls		* refactor role and profile things into proper modules and use proper puppet:// data urls
	* dont' depend on /usr/local/portage/make.conf		* dont' depend on /usr/local/portage/make.conf
			* figure out why the betagarden overlay needs <code>ulimit -n 2048</clone> to clone