On Aug 21, 2:56 pm, Brian Troutwine <br...@troutwine.us> wrote:
> Hello, all.
>
> I have a box that I'd like to have striping swap spaces. I attempted:
>
> mount { 'swap':
> alias => 'swap0',
> atboot => true,
> device => '/dev/xvdo',
> ensure => 'mounted',
> options=> 'defaults',
> fstype => 'swap',
> }
> mount { 'swap':
> alias => 'swap1',
> atboot => true,
> device => '/dev/xvdp',
> ensure => 'mounted',
> options=> 'defaults',
> fstype => 'swap',
> }
>
> and
>
> mount { 'swap0':
> name => 'swap',
> atboot => true,
> device => '/dev/xvdo',
> ensure => 'mounted',
> options=> 'defaults',
> fstype => 'swap',
> }
> mount { 'swap1':
> name => 'swap',
> atboot => true,
> device => '/dev/xvdp',
> ensure => 'mounted',
> options=> 'defaults',
> fstype => 'swap',
> }
>
> to predictable result. Problem is that mount conflates the name of the
> resource with it's mount path; I'm defining the same thing two ways each
> time. I _could_ write out my own fstab as a file resource, but that somewhat
> defeats the purpose of even having a mount type. Am I missing something? Is
> it possible to have multiple swap spaces with puppet?
I'm guessing that this is not supported, but here's a long shot: try
altering your second variation to use the 'path' property instead of
'name' (even though the docs say it's deprecated). Even if that
works, I recommend filing a ticket: I see no inherent reason why
Puppet shouldn't be able to handle this.
John
--
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To post to this group, send email to puppet-users@googlegroups.com.
To unsubscribe from this group, send email to
puppet-users+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en.
