I'm curious if anybody has an experiencing with managing Virtual user
account through Foreman Dashboard? Is it possible to create and delete user
account on the machine trough Foreman dashboard or do I have to keep using
my Puppet files through command line interface?
I'm sorry, but what do you mean by 'Virtual user account'?
···
On Wed, Mar 4, 2015 at 1:59 AM, tyon wrote:
> Hello all,
>
> I'm curious if anybody has an experiencing with managing Virtual user
> account through Foreman Dashboard? Is it possible to create and delete user
> account on the machine trough Foreman dashboard or do I have to keep using
> my Puppet files through command line interface?
>
>
> Many thanks in advance!
>
> --
> You received this message because you are subscribed to the Google Groups
> "Foreman users" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to foreman-users+unsubscribe@googlegroups.com.
> To post to this group, send email to foreman-users@googlegroups.com.
> Visit this group at http://groups.google.com/group/foreman-users.
> For more options, visit https://groups.google.com/d/optout.
Sorry, I will try to explain better what I try to achieve.
During provisioning a new machine or editing an existing one in the Foreman
dashboard I want to be able to choose user accounts which I want to create
on that machine.
I can add different classes from Puppet in the Foreman dashboard and it
works fine (ntp, ssh and etc). With users it's a little different.
Before explaining what I have in Puppet I want to mention that Puppet and
user accounts model was setup before me and I'm still learning Puppet, so I
don't know if it's a good practice
What I have in Puppet right now:
The module Accounts modules/accounts/manifests
This piece from init.pp
class accounts {
include groups*
Class['groups'] -> Class['accounts']*
@accounts::virtual { 'user_name':
group => "group_name",*
realname => 'Mr. Bob',*
pubkey => 'public key',*
state => 'present',*
}*
and so on for all users … }
In my nodes.pp file particular accounts are realized for particular nodes
or in general basenode if this accounts belongs to sysadmin and needs to
exist on every node:
realize (Accounts::Virtual['user_name'])
I hope it's more clear.
Thank you!
···
On Tuesday, March 3, 2015 at 11:41:08 PM UTC-8, Daniel Lobato wrote:
>
> I'm sorry, but what do you mean by 'Virtual user account'?
>
> On Wed, Mar 4, 2015 at 1:59 AM, tyon <surb...@ucdavis.edu > > wrote:
> > Hello all,
> >
> > I'm curious if anybody has an experiencing with managing Virtual user
> > account through Foreman Dashboard? Is it possible to create and delete
> user
> > account on the machine trough Foreman dashboard or do I have to keep
> using
> > my Puppet files through command line interface?
> >
> >
> > Many thanks in advance!
> >
> > --
> > You received this message because you are subscribed to the Google
> Groups
> > "Foreman users" group.
> > To unsubscribe from this group and stop receiving emails from it, send
> an
> > email to foreman-user...@googlegroups.com .
> > To post to this group, send email to forema...@googlegroups.com
> .
> > Visit this group at http://groups.google.com/group/foreman-users.
> > For more options, visit https://groups.google.com/d/optout.
>
>
>
> --
> Daniel Lobato
>
> @elobatoss
> blog.daniellobato.me
> daniellobato.me
>
> GPG: http://keys.gnupg.net/pks/lookup?op=get&search=0x7A92D6DD38D6DE30
>
This is indeed possible, but you'll need to rewrite your manifests.
What you want is a define that creates your user accounts (you
probably already have this as 'accounts::virtual' but you may wish to
change the name to be more clear). Then you'll need a wrapper class
which takes in a hash of data about what users to create, and calls
the define.
I tried the example from the link above with packages first as a proof of
concepts. I really like it, it works exactly how I want for my users. I can
assign different packages/users from the same module to the different
hosts/host groups/domains.
I just cannot understand one thing. When I update my module and add a new
package to the array how I can update it in Foreman GUI?
I tired to do "Import from Puppet" under Configure -> Puppet classes, but
it seems to only import new modules. My array of packages in the current
module stays the same.
Many thanks in advance!
···
On Wednesday, March 4, 2015 at 9:57:37 AM UTC-8, Greg Sutcliffe wrote:
>
> This is indeed possible, but you'll need to rewrite your manifests.
>
> What you want is a define that creates your user accounts (you
> probably already have this as 'accounts::virtual' but you may wish to
> change the name to be more clear). Then you'll need a wrapper class
> which takes in a hash of data about what users to create, and calls
> the define.
>
> You can find more infor here:
>
> http://projects.theforeman.org/projects/foreman/wiki/Instantiate_Puppet_resources
>
> You can also find examples people have used with this pattern by
> searching the archives of this list.
>
> Hope that helps,
> Greg
>
thank you for your help. I figured out that I can change it directly from
Foreman GUI. It works exactly how I want.
Thank a lot!
···
On Wednesday, March 4, 2015 at 10:55:53 PM UTC-8, tyon wrote:
>
> Hi Greg,
>
> Thank you for your answer.
>
> I tried the example from the link above with packages first as a proof of
> concepts. I really like it, it works exactly how I want for my users. I can
> assign different packages/users from the same module to the different
> hosts/host groups/domains.
>
> I just cannot understand one thing. When I update my module and add a new
> package to the array how I can update it in Foreman GUI?
>
> I tired to do "Import from Puppet" under Configure -> Puppet classes, but
> it seems to only import new modules. My array of packages in the current
> module stays the same.
>
> Many thanks in advance!
>
> On Wednesday, March 4, 2015 at 9:57:37 AM UTC-8, Greg Sutcliffe wrote:
>>
>> This is indeed possible, but you'll need to rewrite your manifests.
>>
>> What you want is a define that creates your user accounts (you
>> probably already have this as 'accounts::virtual' but you may wish to
>> change the name to be more clear). Then you'll need a wrapper class
>> which takes in a hash of data about what users to create, and calls
>> the define.
>>
>> You can find more infor here:
>>
>> http://projects.theforeman.org/projects/foreman/wiki/Instantiate_Puppet_resources
>>
>> You can also find examples people have used with this pattern by
>> searching the archives of this list.
>>
>> Hope that helps,
>> Greg
>>
>
I want to manage different user roles on different server groups using
Foreman just like you did. Do you have published your users module
anywhere? I'm pretty new on Puppet and Foreman and to see a real world
working example would help a lot to understand how it works.
Thanks,
Ivan
···
Em segunda-feira, 23 de março de 2015 18:28:09 UTC-3, tyon escreveu:
>
> Hi Greg,
>
> thank you for your help. I figured out that I can change it directly from
> Foreman GUI. It works exactly how I want.
>
> Thank a lot!
>
> On Wednesday, March 4, 2015 at 10:55:53 PM UTC-8, tyon wrote:
>>
>> Hi Greg,
>>
>> Thank you for your answer.
>>
>> I tried the example from the link above with packages first as a proof of
>> concepts. I really like it, it works exactly how I want for my users. I can
>> assign different packages/users from the same module to the different
>> hosts/host groups/domains.
>>
>> I just cannot understand one thing. When I update my module and add a new
>> package to the array how I can update it in Foreman GUI?
>>
>> I tired to do "Import from Puppet" under Configure -> Puppet classes, but
>> it seems to only import new modules. My array of packages in the current
>> module stays the same.
>>
>> Many thanks in advance!
>>
>> On Wednesday, March 4, 2015 at 9:57:37 AM UTC-8, Greg Sutcliffe wrote:
>>>
>>> This is indeed possible, but you'll need to rewrite your manifests.
>>>
>>> What you want is a define that creates your user accounts (you
>>> probably already have this as 'accounts::virtual' but you may wish to
>>> change the name to be more clear). Then you'll need a wrapper class
>>> which takes in a hash of data about what users to create, and calls
>>> the define.
>>>
>>> You can find more infor here:
>>>
>>> http://projects.theforeman.org/projects/foreman/wiki/Instantiate_Puppet_resources
>>>
>>> You can also find examples people have used with this pattern by
>>> searching the archives of this list.
>>>
>>> Hope that helps,
>>> Greg
>>>
>>
