Rewrited git history.
__
This email has been scanned by the MessageLabs Email Security System.
For more information please visit http://www.messagelabs.com/email
Refactorized the aixobject.rb to allow new providers using commands with colon
separated output.
Signed-off-by: Hector Rivas Gandara key...@gmail.com
---
Local-branch: feature/master/5432
lib/puppet/provider/aixobject.rb | 244 --
More elegant Array|String = String conversion in AixObject.
Fixed some bugs and code/comments cleaned.
Signed-off-by: Hector Rivas Gandara key...@gmail.com
---
Local-branch: feature/master/5432
lib/puppet/provider/aixobject.rb | 142 +-
Specific providers should be created for AIX to manage users and groups.
AIX bases the authentication management on a set of commands: mkuser, rmuser,
chuser, lsuser, mkgroup, rmgroup, chgroup, lsg
This commit implements such providers.
The types where extended with:
- feature:
Fixed providers for new aixobject.rb
Fixed incorrect variable naming.
Signed-off-by: Hector Rivas Gandara key...@gmail.com
---
Local-branch: feature/master/5432
lib/puppet/provider/aixobject.rb |8
lib/puppet/provider/group/aix.rb |8 ++--
lib/puppet/provider/user/aix.rb |
Specific providers should be created for AIX to manage users and groups.
AIX bases the authentication management on a set of commands: mkuser, rmuser,
chuser, lsuser, mkgroup, rmgroup, chgroup, lsgroup, etc.
This commit implements such providers.
Notes::
- AIX users can have expiry date
On 28 December 2010 12:04, Hector Rivas Gandara key...@gmail.com wrote:
Modified the facts processorN, processorcount, is_virtual and virtual:
* is_virtual=true and virtual=.zlinux. if architecture=s390x
* /proc/cpuinfo has diferent syntax, matching /processor\s+(\d+):\s+(.*)/
IIRC both
On Jan 8, 2011, at 1:00 PM, James Turnbull wrote:
Thomas Hallgren wrote:
The question I'd like to ask is if it's feasible to use a hack to extract
the needed meta-data without using Ruby, or if
that will break anyway because more Ruby specific code is planned. I love
Ruby, it's a
Thanks.
Any idea how this could be integrated into the Dashboard?
On Jan 9, 2011, at 6:17 PM, Dan Bode wrote:
I finished writing unit tests for this patch. I also wound up refactoring the
patch a little after the unit tests revealed that it could be optimized.
Should I run mail_patches
On Jan 10, 2011, at 10:02 AM, Peter Meier wrote:
Hi
so I found one issue while using the code a bit more in production:
+ def unexport(node)
+# fetch all exported resource
+query = {:include = {:param_values = :param_name}}
+query[:conditions] = [exported=? AND host_id=?,
I'm unsure how to do that in the clean app. Any hints how I could get
the same autoload behavior as one has within the catalog to get it
outside of any scope etc. working?
Without going into the full context of what you're doing, the answer to your
final question is pretty straightforward.
As these options should be available to all applications we move
them into Puppet::Application. This moves also various initialize
and setup code into Puppet::Application.
Signed-off-by: Peter Meier peter.me...@immerda.ch
---
lib/puppet/application.rb| 22 +++---
12 matches
Mail list logo
