On Tue, Jan 24, 2012 at 8:46 AM, Michael Stahnke wrote:
> Which docs? I swear we've had this updated.
These, Mike: http://docs.puppetlabs.com/guides/installing_dashboard.html.
I've pinged Nick Fagerlund about a fix.
Apologies for the bother, Peter. We have this documented in too many place
On Tue, Jan 24, 2012 at 10:56 AM, Peter Berghold
wrote:
> rake aborted!
> no such file to load -- rdoc/task
You may have other issues (aside from the mass of deprecation warnings
... ew), but this makes it look like you're missing the rdoc gem.
r
--
You received this message because you are s
On Fri, May 11, 2012 at 9:43 AM, Pieter van de Bruggen
wrote:
> The connection to the Forge is being established to try to resolve
> dependencies; the `--ignore-dependencies` flag (which is implied by
> `--force`) is what you're looking for. :)
Do we need a more explicit offline mode of operati
On Thu, Jun 28, 2012 at 8:00 PM, Daniel Pittman wrote:
> No, mentioning STDERR is terrible UX, even if I know what it means. :)
>
> I think a better approach would be to capture the error and report it
> meaningfully.
The mockup does that, albeit before the rest of help output. I think
we were
On Fri, Jun 29, 2012 at 10:22 AM, Daniel Pittman wrote:
> So, perhaps the title of that should change from "available
> subcommands" to "all subcommands" or something?
>
> That was the key part that, to me, was worth making that change - that
> these were absolutely *not* available, because they
On Thu, Aug 11, 2011 at 12:40 AM, ki_chi_saga wrote:
>> See the little arrows?
> No i didn't
I think that this is more common than we suspect. It's been on my
list for a while, now I have a ticket:
http://projects.puppetlabs.com/issues/8923
Maybe what we're doing now cannot be improved, bu
Good people ~
We're in an unfortunate situation with Dashboard, having to patch a
bug half-way for the Dashboard 1.2 release because we don't have time
for a complete fix, and because a complete fix may require Puppet
changes.
Within Dashboard's report interface we show links to the filebucket
ev
On Thu, Nov 3, 2011 at 8:38 AM, Nigel Kersten wrote:
> In your puppet.conf agent block:
> ...
> # The maximum time to delay before runs. Defaults to being the same as
> the
> # run interval.
> # The default value is '$runinterval'.
> splaylimit = 1800
Having this uncommented as
#x27;ll be disagreement; right now I'm just gathering requirements.
Once we have feedback from multiple channels we'll work on prioritizing and
creating a roadmap.
Thanks!
r
--
Randall Hansen; Director of User Experience; rand...@puppetlabs.com
--
You received this message because you a
On Mar 2, 2011, at 3:51 PM, Frank Sweetser wrote:
> In this scenario, it would be far more useful to simply use LDAP to verify
> usernames and passwords, and then consult internal records to assign a list
> of roles.
This is a great use case, Frank. What do you mean by "internal records" in
t
On Mar 3, 2011, at 9:20 AM, Brian Gupta wrote:
> Also, going forward, it would be very helpful for the API to be an equal
> citizen of the GUI.
I agree, Brian. While we plan to improve Dashboard's GUI for those who want
it, it's often hard to beat a CLI for efficiency and repeatability.
> Ple
On Mar 3, 2011, at 1:40 PM, Brian Gupta wrote:
>> Absolutely. I'll keep your name on my list, and we'll make our plans in
>> public.
>
> Any sense on a timeframe?
Not at all. I don't like that answer either, but it's the only truth we have.
We'll have a better idea when our roadmap for Dash
Denmat wrote:
Very high level but I would like to see the following:
• to be able to create roles such as viewer, editor, administrator
• these roles be ldap groups
Den, will you tell me more about roles being LDAP groups? To my
perception that could mean:
* Manually creating a role in Das
On Mar 7, 2011, at 3:39 PM, John Warburton wrote:
> Everything everyone else has said plus audit logging of actions taken by the
> user, and ways to report on that (even a "last x changes" on the node view)
Yes, absolutely. RBAC is incomplete without good auditing.
r
--
You received this me
with what you need, either via email or by editing the wiki.
I'm more than happy to insert your cases into the wiki if you don't want to
sign up for an account.
Thank you!
r
--
Randall Hansen • Director of User Experience • rand...@puppetlabs.com
--
You received this message
On Mar 8, 2011, at 2:37 PM, Robin Bowes wrote:
> I'd really like puppet to blow-up at this stage and tell me that I've
> used an variable without defining it first. Those familiar with perl
> will recognise this as "use strict;".
++
r
--
Randall Hansen • Direc
On Mar 8, 2011, at 7:44 AM, Robert Pumphrey wrote:
> I also have a completely blank "Run Time" chart on a new deployment of
> dashboard 1.0.4. Do you have any idea where I might look to try to fix
> this problem?
I see this, too. I'll track it down and post an update her
On Mar 24, 2011, at 9:06 AM, Stefan Goethals wrote:
> Dashboard removes the reports for nodes one by one...
> This can take a long time with many reports.
If this is true (and I have no reason to doubt it), it's Very Bad. I've filed
it as a bug:
http://projects.puppetlabs.com/issues/6828
If t
it start to fall over?
Thank you!
r
--
Randall Hansen • Director of User Experience • rand...@puppetlabs.com
--
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 un
On Apr 4, 2011, at 3:58 PM, FRLinux wrote:
> Have 80 nodes reporting which is not much. Wiped out the whole DB when
> upgraded to 1.0.4, Think it was back in the beginning of November so
> it is same to assume that we've been logging since. Only 10 nodes were
> added in the last month (March).
So
On Tue, Apr 12, 2011 at 4:20 PM, Mohamed Lrhazi wrote:
> Can I import all my existing classes/modules into the dashboard, or do
> I have to create them in the GUI?
Today you have to use the GUI. We know this is a problem, and have
concrete plans to fix it:
http://projects.puppetlabs.com/issues
le every time you type it?
Thanks!
r
--
Randall Hansen • Director of User Experience • rand...@puppetlabs.com
--
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 unsubsc
Good people ~
Is the "resources" type primarily useful for purging? Is it also
commonly used for metaparameters? The documentation[1] says this, but
I haven't used it much myself, and I don't know what common use is.
Thanks!
r
1. http://docs.puppetlabs.com/references/stable/type.html#res
Several people complained that if Puppet's management directories
(e.g., confdir) were symlinks, Puppet would overwrite them with real
directories. It turns out that this issue was a ticket already, and
an old one.
http://projects.puppetlabs.com/issues/650
Please comment on the ticket or reply h
This an existing ticket, too: http://projects.puppetlabs.com/issues/2084
E.g., given:
@file { foo: ... }
@service { bar:
require => File[ foo ]
}
realize Service[ foo ]
File[ foo ] should also be realized.
Please comment on the ticket or reply here, whichever you prefer.
http://projects.puppetlabs.com/issues/7598
If your goal is this (pseudo-code):
@file { "host_one" }
@file { "host_two" }
You should be able to say this:
$array = [ "one", "two" ]
@file { "host_$array" }
Instead of this:
@file { "host_one", "host_two" }
Please comment on t
http://projects.puppetlabs.com/issues/7599
This (or something very like it) should work:
file { foo:
ensure => present
mode => 0644
}
Note the lack of commas after key/value pairs.
Please comment on the ticket or reply here, whichever you prefer.
Thanks!
r
P.S. This i
http://projects.puppetlabs.com/issues/7600
I call this the "agent orange" option :)
This works, purging all unmanaged hosts entries:
resources { 'host':
purge => true,
noop => true,
}
We should have a similar property for all (most?) types.
Please comment on the ticket
http://projects.puppetlabs.com/issues/7601
Our very long docs pages are difficult to use. E.g.,
http://docs.puppetlabs.com/references/2.6.8/type.html
Please comment on the ticket or reply here, whichever you prefer.
Thanks!
r
P.S. This is in response to feedback from my "Improving the Puppet
D
http://projects.puppetlabs.com/issues/7604
import "/etc/puppet/manifests/nodes/*"
Should import all manifests in subdirectories as well.
Note that this conflicts with #4732, which proposes that Puppet globs
act more like shell globs.
Please comment on the ticket or reply here, whichever you
http://projects.puppetlabs.com/issues/7605
The virtual resource operator:
@user { luke: ensure => present }
Is relatively easy to type but, if you don’t know it, very hard to
read. We should consider a word-based syntax, e.g.:
virtual user { luke: ensure => present }
Please comment on
http://projects.puppetlabs.com/issues/7606
The spaceship operator:
User <| group == sysadmin or title == luke |>
Is relatively easy to type but, if you don’t know it, very hard to
read. We should consider a word-based syntax, e.g.:
collect User { group == sysadmin or title == luke }
http://projects.puppetlabs.com/issues/7612
The exported resources syntax:
@@user { luke: ensure => present }
Is concise and powerful, but very difficult to read. We should
consider word-based syntax, e.g.:
export @user { luke: ensure => present }
And taking into account #7605, perhaps:
On Wed, Apr 27, 2011 at 10:34 AM, Aaron Lippold wrote:
> I was wondering if anyone has started on looking at a general data
> graphing framework for visualizing data ( classes, facts, reports ) on
> dashboard.
>
> In the past I have used GDGraph to do this. Has the community talked
> about how we
On Sat, May 28, 2011 at 5:36 AM, Tim Dunphy wrote:
> I noticed that it complained that it couldn't find this file
> /usr/share/puppet-dashboard/public/stylesheets/all.css
This is actually one of the more straightforward aspects of Ruby on
Rails. Everything in the "public" directory is served
On Tue, Jun 7, 2011 at 4:15 PM, Aaron Grewell wrote:
> $users = [{ username => "bill", uid => "12345" },
> { username => "ted", uid => "12346" }]
Aaron, I think this is a completely sane request. We've talked about
it before, but I can't find an existing ticket. This one seems close,
On Wed, Jun 8, 2011 at 12:07 PM, Aaron Grewell wrote:
> All I'm saying is that I think hashes should be first-class citizens in
> Puppet and right now they're not.
I agree with that as a high-level problem statement, but to make
progress we need to put legs on it. John's got one possibility: a
I think Aaron lays out the options pretty well. This issue has been
hanging fire for quite a while, and it would be nice to come to a
decision about what our path forward is.
Who else cares about this? What do you think?
r
On Wed, Jun 8, 2011 at 1:36 PM, Aaron Grewell wrote:
> We've looked at
38 matches
Mail list logo
