<feed xmlns='http://www.w3.org/2005/Atom'>
<title>puppet-gluster.git/manifests/host, branch master</title>
<subtitle>Puppet module for GlusterFS</subtitle>
<link rel='alternate' type='text/html' href='https://fedorapeople.org/cgit/purpleidea/public_git/puppet-gluster.git/'/>
<entry>
<title>Module needs a better description.</title>
<updated>2013-10-10T22:26:13+00:00</updated>
<author>
<name>James Shubin</name>
<email>james@shubin.ca</email>
</author>
<published>2013-10-10T22:26:13+00:00</published>
<link rel='alternate' type='text/html' href='https://fedorapeople.org/cgit/purpleidea/public_git/puppet-gluster.git/commit/?id=b9153d8859b11d9672ba285dc0f281b0bdf78119'/>
<id>b9153d8859b11d9672ba285dc0f281b0bdf78119</id>
<content type='text'>
While the module can still be used in a simple way:

* It is pretty complicated at this point. It does some advanced stuff.
* I wanted to avoid confusion with gluster::simple which is coming soon.
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
While the module can still be used in a simple way:

* It is pretty complicated at this point. It does some advanced stuff.
* I wanted to avoid confusion with gluster::simple which is coming soon.
</pre>
</div>
</content>
</entry>
<entry>
<title>Finally, Fancy Firewalling...</title>
<updated>2013-09-18T09:52:23+00:00</updated>
<author>
<name>James Shubin</name>
<email>james@shubin.ca</email>
</author>
<published>2013-09-18T09:52:23+00:00</published>
<link rel='alternate' type='text/html' href='https://fedorapeople.org/cgit/purpleidea/public_git/puppet-gluster.git/commit/?id=4dbba38fc44e8d7226fdecec12b1237fc24d026d'/>
<id>4dbba38fc44e8d7226fdecec12b1237fc24d026d</id>
<content type='text'>
This adds experimental support for automatic firewalling. Initially, we
don't know the other hosts (until they are exported and collected) so we
start with an blank firewall to all hosts. After hosts start checking
in, we start only allowing specify host ips. For the volume building, we
can't predict (AFAICT) which ports will be used until after the volume
is started, so we initially allow all ports inbound, until the fact gets
the data from the started volume and uses those specific ports. This
naturally takes multiple puppet runs to complete.
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
This adds experimental support for automatic firewalling. Initially, we
don't know the other hosts (until they are exported and collected) so we
start with an blank firewall to all hosts. After hosts start checking
in, we start only allowing specify host ips. For the volume building, we
can't predict (AFAICT) which ports will be used until after the volume
is started, so we initially allow all ports inbound, until the fact gets
the data from the started volume and uses those specific ports. This
naturally takes multiple puppet runs to complete.
</pre>
</div>
</content>
</entry>
</feed>
