On 3/27/13 11:35 PM, rob_hirschf...@dell.com wrote:
> All excellent points.
>
> I think that we need to distinguish between the framework and the content for
> discussion.
>
> To me, your comments are about content gaps (which are significant).
Yes, I agree. In general I have no problems with the
All excellent points.
I think that we need to distinguish between the framework and the content for
discussion.
To me, your comments are about content gaps (which are significant).
There are some framework gaps (like PDF output) that can be addressed as we
progress.
Are you OK w/ the framewor
On 3/27/13 10:27 PM, rob_hirschf...@dell.com wrote:
> No - I'm saying to embed them. Let me explain.
Right, this is what I understood.
>
> We've created a system that consolidates all the docs into a consistent place
> and breaks them into manageable parts. We're maintaining all of the docs in
No - I'm saying to embed them. Let me explain.
We've created a system that consolidates all the docs into a consistent place
and breaks them into manageable parts. We're maintaining all of the docs in
that way. That seems like a very good thing to me.
We've create a way to export all of the
On 03/27/2013 07:57 PM, Kenneth Wimer wrote:
>>
>> Where would you see the developer docs link?
> Typically, I would expect the developer docs to be on the wiki in
> github. I have nothing against showing them in the System
> Documentation in development mode but a) it seems like the last place
On 3/27/13 7:29 PM, rob_hirschf...@dell.com wrote:
> +1
>
> Where would you see the developer docs link?
Typically, I would expect the developer docs to be on the wiki in
github. I have nothing against showing them in the System Documentation
in development mode but a) it seems like the last plac
+1
Where would you see the developer docs link?
-Original Message-
From: crowbar-bounces On Behalf Of Kenneth Wimer
Sent: Wednesday, March 27, 2013 10:49 AM
To: James Tan
Cc: crowbar
Subject: Re: [Crowbar] System Documentation UI
On 3/27/13 3:49 PM, James Tan wrote:
> On 03/27/2013 03:0
Your disk space might get full again unless you run a compaction on CouchDB.
Run the following command as a cron job to keep you’re the couch DB size in
control:
curl -H "Content-Type: application/json" -X POST
http://localhost:5984/chef/_compact
Regards~hrushi
From: crowbar-boun...@dell.com [
Thanks Victor.
Along those lines, I'm working on the inbound data path. I had been using
JigMap to do this but it's going to require some more design discussion to
complete. Instead, I'm planning to hardwire the few inbound attribs into each
barclamp.process_inbound_data routines.
This is
After kicking around what is needed between Ward, Wayne and myself, we
came up with the minimal definition of a "job" for Crowbar.
1: Transition request for a node gets put to the framework
2: Node transition function iterates over all active and pending
deployments on it, pulling in any attribs,
Hello,
I know it is an old thread but I ran into the same problem recently:
- impossible to connect to crowbar webui on port 3000
- impossible to connect to chef on port 4000 and 4040
- restarting chef-server service failed.
Finally I found out that I had no space left on disk due to the chef'
On 3/27/13 3:49 PM, James Tan wrote:
> On 03/27/2013 03:02 PM, Kenneth Wimer wrote:
>> I noticed the typos already and fixed them in the SVG file. BTW, I
>> made all of this with inkscape so if someone is interested in the
>> source files I'll put them in the repo as well.
>
> Sweet. Yes why not
On 03/27/2013 03:02 PM, Kenneth Wimer wrote:
> I noticed the typos already and fixed them in the SVG file. BTW, I
> made all of this with inkscape so if someone is interested in the
> source files I'll put them in the repo as well.
Sweet. Yes why not just push the .svg in - I think most modern b
On 3/27/13 2:57 PM, James Tan wrote:
> Hi Ken,
>
> On 03/27/2013 02:24 PM, Kenneth Wimer wrote:
>> I did a heuristic evaluation of the System Documentation and made a list
>> of possible bugs and simple improvements. I only worked on the
>> production version so the Developers Guide and such were n
Hi Ken,
On 03/27/2013 02:24 PM, Kenneth Wimer wrote:
> I did a heuristic evaluation of the System Documentation and made a list
> of possible bugs and simple improvements. I only worked on the
> production version so the Developers Guide and such were not part of the
> scope. All of my notes as we
Hi,
I did a heuristic evaluation of the System Documentation and made a list
of possible bugs and simple improvements. I only worked on the
production version so the Developers Guide and such were not part of the
scope. All of my notes as well as wire-frames are available at:
https://github.co
Hi,
On Tue, Mar 26, 2013 at 10:56:14PM +0100, Dirk Müller wrote:
> 2013/3/26 Ralf Haferkamp :
>
> Hi Ralf,
> > It turned out to be not a bug in the kernel but in the %post scriptlet of
> > the
> > grub package. Until that is fixed (which is hopefully not too far away) I
> > added
> > a grub pac
17 matches
Mail list logo
