Puppet users - May 2011 - Dashboard 1.1.0rc1 - How to destroy node when site is readonly?

Partly for security, but mostly for avoiding mistakes, I''ve configured
dashboard in read-only mode in settings.yml(enable_read_only_mode:
true).

If I want to now delete a node from the dashboard is there a way I can
do this?

I''ve had a look at the node rake task and can see I can add a new
node, but can''t see a method to destroy/delete a node.

Also if this is possible, what happens to all the reports for this
node in the database?  Are they orphaned or are they removed as well?

Oh, and I''m not using enternal node classification.

Thanks.

-- 
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+unsubscribe@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en.

On Wed, May 11, 2011 at 1:21 AM, scarts <stephenandmindi@me.com> wrote:
> Partly for security, but mostly for avoiding mistakes, I''ve
configured
> dashboard in read-only mode in settings.yml(enable_read_only_mode:
> true).
>
> If I want to now delete a node from the dashboard is there a way I can
> do this?
>
A number of sites are configuring two Apache virtual hosts with two copies
of the dashboard code connected to the same database instance.  The first
interface is read-only and widely available to the organization to allow
people to view reports, etc...

This is: http://projects.puppetlabs.com/issues/5217

The second interface uses Apache access controls to allow only authorized
people to log in and write to the database, e.g. define new nodes, classes,
and delete nodes.

This is a stopgap until proper RBAC is added as a feature of the Dashboard.
I believe the ticket to watch for this feature is:

http://projects.puppetlabs.com/issues/3219

> I''ve had a look at the node rake task and can see I can add a new
> node, but can''t see a method to destroy/delete a node.
>
> Also if this is possible, what happens to all the reports for this
> node in the database?  Are they orphaned or are they removed as well?
>
I''m not sure the answer to this question.  Perhaps someone more
familiar
with the internals will be able to respond, I''ve pinged my colleagues
to
find out.

> Oh, and I''m not using enternal node classification.
>
The ENC portion of the UI can also be selectively disabled.  Please see:

http://projects.puppetlabs.com/issues/4474

Hope this helps,
-- 
Jeff McCune
Puppet Labs
@0xEFF

-- 
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+unsubscribe@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en.

On 11 May 2011, at 22:22, Jeff McCune <jeff@puppetlabs.com> wrote:
> On Wed, May 11, 2011 at 1:21 AM, scarts <stephenandmindi@me.com>
wrote:
> Partly for security, but mostly for avoiding mistakes, I''ve
configured
> dashboard in read-only mode in settings.yml(enable_read_only_mode:
> true).
> 
> If I want to now delete a node from the dashboard is there a way I can
> do this?
> 
> A number of sites are configuring two Apache virtual hosts with two copies
of the dashboard code connected to the same database instance.  The first
interface is read-only and widely available to the organization to allow people
to view reports, etc...
> 
> This is: http://projects.puppetlabs.com/issues/5217
> 
> The second interface uses Apache access controls to allow only authorized
people to log in and write to the database, e.g. define new nodes, classes, and
delete nodes.
> 
> This is a stopgap until proper RBAC is added as a feature of the Dashboard.
I believe the ticket to watch for this feature is:
> 
> http://projects.puppetlabs.com/issues/3219
>  
> I''ve had a look at the node rake task and can see I can add a new
> node, but can''t see a method to destroy/delete a node.
> 
> Also if this is possible, what happens to all the reports for this
> node in the database?  Are they orphaned or are they removed as well?
> 
> I''m not sure the answer to this question.  Perhaps someone more
familiar with the internals will be able to respond, I''ve pinged my
colleagues to find out.
>  
> Oh, and I''m not using enternal node classification.
> 
> The ENC portion of the UI can also be selectively disabled.  Please see:
> 
> http://projects.puppetlabs.com/issues/4474
> 
> Hope this helps,
> -- 
> Jeff McCune
> Puppet Labs
> @0xEFF
> -- 
> 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+unsubscribe@googlegroups.com.
> For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en.
Thanks Jeff for such a detailed reply. I''ll watch the ldap auth ticket
as that would solve a lot of ''like to have'' features in one
go.

The workaround, now that you mention it, seems almost obvious now so
I''ll look at setting that up, although a rake task would be just as
good (possibly better to support mass deletes) for myself at least.
I''ll try to poke around the code to see how how the destroy button in
the UI works to see if i can hack/copy functionality into a rake task.

Also thanks for the feature link to disabling external node feature in dashboard
- I already have that set.

-- 
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+unsubscribe@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en.