Just in case anyone is listening, I just checked in a significant changeset to the aspen trunk. I've folded the aspen.monitord script into aspen itself. This means that the same infrastructure used in development mode to restart the server when source files change is now also used in production mode to restart the server if/when the main (child) server process ever dies unexpectedly.
This update also includes logging configuration changes, as well as tests for all changes. Once this update settles and I can bring the documentation up to date, I plan to issue a point release in the 0.8 line.
Thanks for listening. Would love any feedback on the latest changes.
On Wed, Feb 11, 2009 at 6:59 AM, Chad Whitacre <c...@zetaweb.com> wrote:
> Greetings,
> Just in case anyone is listening, I just checked in a significant
> changeset to the aspen trunk. I've folded the aspen.monitord
> script into aspen itself. This means that the same infrastructure
> used in development mode to restart the server when source files
> change is now also used in production mode to restart the server
> if/when the main (child) server process ever dies unexpectedly.
> This update also includes logging configuration changes, as well
> as tests for all changes. Once this update settles and I can
> bring the documentation up to date, I plan to issue a point
> release in the 0.8 line.
> Thanks for listening. Would love any feedback on the latest changes.
> chad
-- ---
NOTE: If it is important CALL ME - I may miss email
---
LD Landis - N0YRQ - de la tierra del encanto
3960 Schooner Loop, Las Cruces, NM 88012
651/340-4007 N32 21'48.28" W106 46'5.80"
"If a thing is worth doing,
it is worth doing badly." –GK Chesterton.
An interpretation: For things worth doing: Doing them, even if badly,
is better than doing nothing perfectly (on them).
Definitely understand the $ issue, I'm experiencing that too. Haven't even started on Python 3 support for that very reason. :^/
The dev snapshots on zetadev.com are tracking trunk/, so they are up to date, yes. When I get some docs written they'll show up there too; likewise with the point release.
Care to say anymore about how you're using aspen? It's always good to hear real-world use cases.
> What is there is the version that I am currently
> running.
> So, where are you on moving to Python 3?
> Cheers,
> --ldl
> On Wed, Feb 11, 2009 at 6:59 AM, Chad Whitacre <c...@zetaweb.com> wrote:
>> Greetings,
>> Just in case anyone is listening, I just checked in a significant
>> changeset to the aspen trunk. I've folded the aspen.monitord
>> script into aspen itself. This means that the same infrastructure
>> used in development mode to restart the server when source files
>> change is now also used in production mode to restart the server
>> if/when the main (child) server process ever dies unexpectedly.
>> This update also includes logging configuration changes, as well
>> as tests for all changes. Once this update settles and I can
>> bring the documentation up to date, I plan to issue a point
>> release in the 0.8 line.
>> Thanks for listening. Would love any feedback on the latest changes.
I have a gig at a major medical clinic supporting the
primary laboratory system.
The system is sort of "locked down" in that they don't
want a lot of "other" stuff running there.
I talked them into installing the IBM/AIX C compiler
on a non-production box, and proceeded to build up
a collection of tools: python, gnuplot, etc... and installed
the executables on the production box.
We collect data about the running application, # users,
# transactions / 5 minute period, size of the various
database tables, lots of stuff... then plot it to .png files.
Aspen then provides the web server that lets the mgmt
types look at the various graphs (which keeps them off
of our backs and entertains them)... It has proven to be
very helpful when having *those* discussions with the
various system administrators and the SAN team....
They'll start spinning some story, and so we just ask
them how that relates to this or that graph... which means
that we actually get some solutions to our complaints!
Right now, the internal site is pretty static, but I am
hoping to revamp it some over the next few months.
Aspen is great for the simple things we have to do,
and we haven't even done the cool stuff yet!
On Wed, Feb 11, 2009 at 11:46 AM, Chad Whitacre <c...@zetaweb.com> wrote:
> Gus,
> Definitely understand the $ issue, I'm experiencing that too. Haven't even
> started on Python 3 support for that very reason. :^/
> The dev snapshots on zetadev.com are tracking trunk/, so they are up to
> date, yes. When I get some docs written they'll show up there too; likewise
> with the point release.
> Care to say anymore about how you're using aspen? It's always good to hear
> real-world use cases.
> chad
> LD 'Gus' Landis wrote:
>> Chad,
>> Listening and encouraged!
>> I am disappointed in my level of effort helping on this,
>> but earning $ has been in the way of that.
>> Glad to see some movement on aspen, it is a nice
>> tool and has been serving some internal needs well.
>> I am planning to revamp the existing internal aspen
>> site and will plan to move up to this new release.
>> What is there is the version that I am currently
>> running.
>> So, where are you on moving to Python 3?
>> Cheers,
>> --ldl
>> On Wed, Feb 11, 2009 at 6:59 AM, Chad Whitacre <c...@zetaweb.com> wrote:
>>> Greetings,
>>> Just in case anyone is listening, I just checked in a significant
>>> changeset to the aspen trunk. I've folded the aspen.monitord
>>> script into aspen itself. This means that the same infrastructure
>>> used in development mode to restart the server when source files
>>> change is now also used in production mode to restart the server
>>> if/when the main (child) server process ever dies unexpectedly.
>>> This update also includes logging configuration changes, as well
>>> as tests for all changes. Once this update settles and I can
>>> bring the documentation up to date, I plan to issue a point
>>> release in the 0.8 line.
>>> Thanks for listening. Would love any feedback on the latest changes.
>>> chad
-- ---
NOTE: If it is important CALL ME - I may miss email
---
LD Landis - N0YRQ - de la tierra del encanto
3960 Schooner Loop, Las Cruces, NM 88012
651/340-4007 N32 21'48.28" W106 46'5.80"
"If a thing is worth doing,
it is worth doing badly." –GK Chesterton.
An interpretation: For things worth doing: Doing them, even if badly,
is better than doing nothing perfectly (on them).
> I have a gig at a major medical clinic supporting the
> primary laboratory system.
> The system is sort of "locked down" in that they don't
> want a lot of "other" stuff running there.
> I talked them into installing the IBM/AIX C compiler
> on a non-production box, and proceeded to build up
> a collection of tools: python, gnuplot, etc... and installed
> the executables on the production box.
> We collect data about the running application, # users,
> # transactions / 5 minute period, size of the various
> database tables, lots of stuff... then plot it to .png files.
> Aspen then provides the web server that lets the mgmt
> types look at the various graphs (which keeps them off
> of our backs and entertains them)... It has proven to be
> very helpful when having *those* discussions with the
> various system administrators and the SAN team....
> They'll start spinning some story, and so we just ask
> them how that relates to this or that graph... which means
> that we actually get some solutions to our complaints!
> Right now, the internal site is pretty static, but I am
> hoping to revamp it some over the next few months.
> Aspen is great for the simple things we have to do,
> and we haven't even done the cool stuff yet!
> Cheers,
> --ldl
> On Wed, Feb 11, 2009 at 11:46 AM, Chad Whitacre <c...@zetaweb.com> wrote:
>> Gus,
>> Definitely understand the $ issue, I'm experiencing that too. Haven't even
>> started on Python 3 support for that very reason. :^/
>> The dev snapshots on zetadev.com are tracking trunk/, so they are up to
>> date, yes. When I get some docs written they'll show up there too; likewise
>> with the point release.
>> Care to say anymore about how you're using aspen? It's always good to hear
>> real-world use cases.
>> chad
>> LD 'Gus' Landis wrote:
>>> Chad,
>>> Listening and encouraged!
>>> I am disappointed in my level of effort helping on this,
>>> but earning $ has been in the way of that.
>>> Glad to see some movement on aspen, it is a nice
>>> tool and has been serving some internal needs well.
>>> I am planning to revamp the existing internal aspen
>>> site and will plan to move up to this new release.
>>> What is there is the version that I am currently
>>> running.
>>> So, where are you on moving to Python 3?
>>> Cheers,
>>> --ldl
>>> On Wed, Feb 11, 2009 at 6:59 AM, Chad Whitacre <c...@zetaweb.com> wrote:
>>>> Greetings,
>>>> Just in case anyone is listening, I just checked in a significant
>>>> changeset to the aspen trunk. I've folded the aspen.monitord
>>>> script into aspen itself. This means that the same infrastructure
>>>> used in development mode to restart the server when source files
>>>> change is now also used in production mode to restart the server
>>>> if/when the main (child) server process ever dies unexpectedly.
>>>> This update also includes logging configuration changes, as well
>>>> as tests for all changes. Once this update settles and I can
>>>> bring the documentation up to date, I plan to issue a point
>>>> release in the 0.8 line.
>>>> Thanks for listening. Would love any feedback on the latest changes.
>>>> chad
> --
> ---
> NOTE: If it is important CALL ME - I may miss email
> ---
> LD Landis - N0YRQ - de la tierra del encanto
> 3960 Schooner Loop, Las Cruces, NM 88012
> 651/340-4007 N32 21'48.28" W106 46'5.80"
> "If a thing is worth doing,
> it is worth doing badly." –GK Chesterton.
> An interpretation: For things worth doing: Doing them, even if badly,
> is better than doing nothing perfectly (on them).
-- ---
NOTE: If it is important CALL ME - I may miss email
---
LD Landis - N0YRQ - de la tierra del encanto
3960 Schooner Loop, Las Cruces, NM 88012
651/340-4007 N32 21'48.28" W106 46'5.80"
"If a thing is worth doing,
it is worth doing badly." –GK Chesterton.
An interpretation: For things worth doing: Doing them, even if badly,
is better than doing nothing perfectly (on them).
> I have a gig at a major medical clinic supporting the
> primary laboratory system.
> The system is sort of "locked down" in that they don't
> want a lot of "other" stuff running there.
> I talked them into installing the IBM/AIX C compiler
> on a non-production box, and proceeded to build up
> a collection of tools: python, gnuplot, etc... and installed
> the executables on the production box.
> We collect data about the running application, # users,
> # transactions / 5 minute period, size of the various
> database tables, lots of stuff... then plot it to .png files.
> Aspen then provides the web server that lets the mgmt
> types look at the various graphs (which keeps them off
> of our backs and entertains them)... It has proven to be
> very helpful when having *those* discussions with the
> various system administrators and the SAN team....
> They'll start spinning some story, and so we just ask
> them how that relates to this or that graph... which means
> that we actually get some solutions to our complaints!
> Right now, the internal site is pretty static, but I am
> hoping to revamp it some over the next few months.
> Aspen is great for the simple things we have to do,
> and we haven't even done the cool stuff yet!
> Cheers,
> --ldl
> On Wed, Feb 11, 2009 at 11:46 AM, Chad Whitacre <c...@zetaweb.com> wrote:
>> Gus,
>> Definitely understand the $ issue, I'm experiencing that too. Haven't even
>> started on Python 3 support for that very reason. :^/
>> The dev snapshots on zetadev.com are tracking trunk/, so they are up to
>> date, yes. When I get some docs written they'll show up there too; likewise
>> with the point release.
>> Care to say anymore about how you're using aspen? It's always good to hear
>> real-world use cases.
>> chad
>> LD 'Gus' Landis wrote:
>>> Chad,
>>> Listening and encouraged!
>>> I am disappointed in my level of effort helping on this,
>>> but earning $ has been in the way of that.
>>> Glad to see some movement on aspen, it is a nice
>>> tool and has been serving some internal needs well.
>>> I am planning to revamp the existing internal aspen
>>> site and will plan to move up to this new release.
>>> What is there is the version that I am currently
>>> running.
>>> So, where are you on moving to Python 3?
>>> Cheers,
>>> --ldl
>>> On Wed, Feb 11, 2009 at 6:59 AM, Chad Whitacre <c...@zetaweb.com> wrote:
>>>> Greetings,
>>>> Just in case anyone is listening, I just checked in a significant
>>>> changeset to the aspen trunk. I've folded the aspen.monitord
>>>> script into aspen itself. This means that the same infrastructure
>>>> used in development mode to restart the server when source files
>>>> change is now also used in production mode to restart the server
>>>> if/when the main (child) server process ever dies unexpectedly.
>>>> This update also includes logging configuration changes, as well
>>>> as tests for all changes. Once this update settles and I can
>>>> bring the documentation up to date, I plan to issue a point
>>>> release in the 0.8 line.
>>>> Thanks for listening. Would love any feedback on the latest changes.
On Thu, Feb 12, 2009 at 12:39 PM, Chad Whitacre <c...@zetaweb.com> wrote:
> This is great, Gus, thanks. So aspen works for you because it's pure Python?
> Easy to install in a "locked down" environment?
> chad
> LD 'Gus' Landis wrote:
>> Chad,
>> I have a gig at a major medical clinic supporting the
>> primary laboratory system.
>> The system is sort of "locked down" in that they don't
>> want a lot of "other" stuff running there.
>> I talked them into installing the IBM/AIX C compiler
>> on a non-production box, and proceeded to build up
>> a collection of tools: python, gnuplot, etc... and installed
>> the executables on the production box.
>> We collect data about the running application, # users,
>> # transactions / 5 minute period, size of the various
>> database tables, lots of stuff... then plot it to .png files.
>> Aspen then provides the web server that lets the mgmt
>> types look at the various graphs (which keeps them off
>> of our backs and entertains them)... It has proven to be
>> very helpful when having *those* discussions with the
>> various system administrators and the SAN team....
>> They'll start spinning some story, and so we just ask
>> them how that relates to this or that graph... which means
>> that we actually get some solutions to our complaints!
>> Right now, the internal site is pretty static, but I am
>> hoping to revamp it some over the next few months.
>> Aspen is great for the simple things we have to do,
>> and we haven't even done the cool stuff yet!
>> Cheers,
>> --ldl
>> On Wed, Feb 11, 2009 at 11:46 AM, Chad Whitacre <c...@zetaweb.com> wrote:
>>> Gus,
>>> Definitely understand the $ issue, I'm experiencing that too. Haven't
>>> even
>>> started on Python 3 support for that very reason. :^/
>>> The dev snapshots on zetadev.com are tracking trunk/, so they are up to
>>> date, yes. When I get some docs written they'll show up there too;
>>> likewise
>>> with the point release.
>>> Care to say anymore about how you're using aspen? It's always good to
>>> hear
>>> real-world use cases.
>>> chad
>>> LD 'Gus' Landis wrote:
>>>> Chad,
>>>> Listening and encouraged!
>>>> I am disappointed in my level of effort helping on this,
>>>> but earning $ has been in the way of that.
>>>> Glad to see some movement on aspen, it is a nice
>>>> tool and has been serving some internal needs well.
>>>> I am planning to revamp the existing internal aspen
>>>> site and will plan to move up to this new release.
>>>> What is there is the version that I am currently
>>>> running.
>>>> So, where are you on moving to Python 3?
>>>> Cheers,
>>>> --ldl
>>>> On Wed, Feb 11, 2009 at 6:59 AM, Chad Whitacre <c...@zetaweb.com> wrote:
>>>>> Greetings,
>>>>> Just in case anyone is listening, I just checked in a significant
>>>>> changeset to the aspen trunk. I've folded the aspen.monitord
>>>>> script into aspen itself. This means that the same infrastructure
>>>>> used in development mode to restart the server when source files
>>>>> change is now also used in production mode to restart the server
>>>>> if/when the main (child) server process ever dies unexpectedly.
>>>>> This update also includes logging configuration changes, as well
>>>>> as tests for all changes. Once this update settles and I can
>>>>> bring the documentation up to date, I plan to issue a point
>>>>> release in the 0.8 line.
>>>>> Thanks for listening. Would love any feedback on the latest changes.
-- ---
NOTE: If it is important CALL ME - I may miss email
---
LD Landis - N0YRQ - de la tierra del encanto
3960 Schooner Loop, Las Cruces, NM 88012
651/340-4007 N32 21'48.28" W106 46'5.80"
"If a thing is worth doing,
it is worth doing badly." –GK Chesterton.
An interpretation: For things worth doing: Doing them, even if badly,
is better than doing nothing perfectly (on them).
LD 'Gus' Landis wrote:
> Yup, and from just a regular, unprivileged user account
> (of course, I can't use port 80, but 8080 is almost as
> well known).
> On Thu, Feb 12, 2009 at 12:39 PM, Chad Whitacre <c...@zetaweb.com> wrote:
>> This is great, Gus, thanks. So aspen works for you because it's pure Python?
>> Easy to install in a "locked down" environment?
>> chad
>> LD 'Gus' Landis wrote:
>>> Chad,
>>> I have a gig at a major medical clinic supporting the
>>> primary laboratory system.
>>> The system is sort of "locked down" in that they don't
>>> want a lot of "other" stuff running there.
>>> I talked them into installing the IBM/AIX C compiler
>>> on a non-production box, and proceeded to build up
>>> a collection of tools: python, gnuplot, etc... and installed
>>> the executables on the production box.
>>> We collect data about the running application, # users,
>>> # transactions / 5 minute period, size of the various
>>> database tables, lots of stuff... then plot it to .png files.
>>> Aspen then provides the web server that lets the mgmt
>>> types look at the various graphs (which keeps them off
>>> of our backs and entertains them)... It has proven to be
>>> very helpful when having *those* discussions with the
>>> various system administrators and the SAN team....
>>> They'll start spinning some story, and so we just ask
>>> them how that relates to this or that graph... which means
>>> that we actually get some solutions to our complaints!
>>> Right now, the internal site is pretty static, but I am
>>> hoping to revamp it some over the next few months.
>>> Aspen is great for the simple things we have to do,
>>> and we haven't even done the cool stuff yet!
>>> Cheers,
>>> --ldl
>>> On Wed, Feb 11, 2009 at 11:46 AM, Chad Whitacre <c...@zetaweb.com> wrote:
>>>> Gus,
>>>> Definitely understand the $ issue, I'm experiencing that too. Haven't
>>>> even
>>>> started on Python 3 support for that very reason. :^/
>>>> The dev snapshots on zetadev.com are tracking trunk/, so they are up to
>>>> date, yes. When I get some docs written they'll show up there too;
>>>> likewise
>>>> with the point release.
>>>> Care to say anymore about how you're using aspen? It's always good to
>>>> hear
>>>> real-world use cases.
>>>> chad
>>>> LD 'Gus' Landis wrote:
>>>>> Chad,
>>>>> Listening and encouraged!
>>>>> I am disappointed in my level of effort helping on this,
>>>>> but earning $ has been in the way of that.
>>>>> Glad to see some movement on aspen, it is a nice
>>>>> tool and has been serving some internal needs well.
>>>>> I am planning to revamp the existing internal aspen
>>>>> site and will plan to move up to this new release.
>>>>> What is there is the version that I am currently
>>>>> running.
>>>>> So, where are you on moving to Python 3?
>>>>> Cheers,
>>>>> --ldl
>>>>> On Wed, Feb 11, 2009 at 6:59 AM, Chad Whitacre <c...@zetaweb.com> wrote:
>>>>>> Greetings,
>>>>>> Just in case anyone is listening, I just checked in a significant
>>>>>> changeset to the aspen trunk. I've folded the aspen.monitord
>>>>>> script into aspen itself. This means that the same infrastructure
>>>>>> used in development mode to restart the server when source files
>>>>>> change is now also used in production mode to restart the server
>>>>>> if/when the main (child) server process ever dies unexpectedly.
>>>>>> This update also includes logging configuration changes, as well
>>>>>> as tests for all changes. Once this update settles and I can
>>>>>> bring the documentation up to date, I plan to issue a point
>>>>>> release in the 0.8 line.
>>>>>> Thanks for listening. Would love any feedback on the latest changes.
NONO NOOOO! It is on AIX. The screenshots from the
Microsoft Impaired system is because I have to use their
funky VPN (which I haven't bothered to work out a real
solution for)...
So snapshots were from a VirtualBox hosted Microsoft
Windows 2000 instance running on Intrepid Ibex Ubuntu,
operating with their funky VPN.
On Thu, Feb 12, 2009 at 1:43 PM, Chad Whitacre <c...@zetaweb.com> wrote:
> And are you running it on Windows? Or just hitting it from Windows in the
> screenshots?
> chad
> LD 'Gus' Landis wrote:
>> Yup, and from just a regular, unprivileged user account
>> (of course, I can't use port 80, but 8080 is almost as
>> well known).
>> On Thu, Feb 12, 2009 at 12:39 PM, Chad Whitacre <c...@zetaweb.com> wrote:
>>> This is great, Gus, thanks. So aspen works for you because it's pure
>>> Python?
>>> Easy to install in a "locked down" environment?
>>> chad
>>> LD 'Gus' Landis wrote:
>>>> Chad,
>>>> I have a gig at a major medical clinic supporting the
>>>> primary laboratory system.
>>>> The system is sort of "locked down" in that they don't
>>>> want a lot of "other" stuff running there.
>>>> I talked them into installing the IBM/AIX C compiler
>>>> on a non-production box, and proceeded to build up
>>>> a collection of tools: python, gnuplot, etc... and installed
>>>> the executables on the production box.
>>>> We collect data about the running application, # users,
>>>> # transactions / 5 minute period, size of the various
>>>> database tables, lots of stuff... then plot it to .png files.
>>>> Aspen then provides the web server that lets the mgmt
>>>> types look at the various graphs (which keeps them off
>>>> of our backs and entertains them)... It has proven to be
>>>> very helpful when having *those* discussions with the
>>>> various system administrators and the SAN team....
>>>> They'll start spinning some story, and so we just ask
>>>> them how that relates to this or that graph... which means
>>>> that we actually get some solutions to our complaints!
>>>> Right now, the internal site is pretty static, but I am
>>>> hoping to revamp it some over the next few months.
>>>> Aspen is great for the simple things we have to do,
>>>> and we haven't even done the cool stuff yet!
>>>> Cheers,
>>>> --ldl
>>>> On Wed, Feb 11, 2009 at 11:46 AM, Chad Whitacre <c...@zetaweb.com>
>>>> wrote:
>>>>> Gus,
>>>>> Definitely understand the $ issue, I'm experiencing that too. Haven't
>>>>> even
>>>>> started on Python 3 support for that very reason. :^/
>>>>> The dev snapshots on zetadev.com are tracking trunk/, so they are up to
>>>>> date, yes. When I get some docs written they'll show up there too;
>>>>> likewise
>>>>> with the point release.
>>>>> Care to say anymore about how you're using aspen? It's always good to
>>>>> hear
>>>>> real-world use cases.
>>>>> chad
>>>>> LD 'Gus' Landis wrote:
>>>>>> Chad,
>>>>>> Listening and encouraged!
>>>>>> I am disappointed in my level of effort helping on this,
>>>>>> but earning $ has been in the way of that.
>>>>>> Glad to see some movement on aspen, it is a nice
>>>>>> tool and has been serving some internal needs well.
>>>>>> I am planning to revamp the existing internal aspen
>>>>>> site and will plan to move up to this new release.
>>>>>> What is there is the version that I am currently
>>>>>> running.
>>>>>> So, where are you on moving to Python 3?
>>>>>> Cheers,
>>>>>> --ldl
>>>>>> On Wed, Feb 11, 2009 at 6:59 AM, Chad Whitacre <c...@zetaweb.com>
>>>>>> wrote:
>>>>>>> Greetings,
>>>>>>> Just in case anyone is listening, I just checked in a significant
>>>>>>> changeset to the aspen trunk. I've folded the aspen.monitord
>>>>>>> script into aspen itself. This means that the same infrastructure
>>>>>>> used in development mode to restart the server when source files
>>>>>>> change is now also used in production mode to restart the server
>>>>>>> if/when the main (child) server process ever dies unexpectedly.
>>>>>>> This update also includes logging configuration changes, as well
>>>>>>> as tests for all changes. Once this update settles and I can
>>>>>>> bring the documentation up to date, I plan to issue a point
>>>>>>> release in the 0.8 line.
>>>>>>> Thanks for listening. Would love any feedback on the latest changes.
-- ---
NOTE: If it is important CALL ME - I may miss email
---
LD Landis - N0YRQ - de la tierra del encanto
3960 Schooner Loop, Las Cruces, NM 88012
651/340-4007 N32 21'48.28" W106 46'5.80"
"If a thing is worth doing,
it is worth doing badly." –GK Chesterton.
An interpretation: For things worth doing: Doing them, even if badly,
is better than doing nothing perfectly (on them).
LD 'Gus' Landis wrote:
> NONO NOOOO! It is on AIX. The screenshots from the
> Microsoft Impaired system is because I have to use their
> funky VPN (which I haven't bothered to work out a real
> solution for)...
> So snapshots were from a VirtualBox hosted Microsoft
> Windows 2000 instance running on Intrepid Ibex Ubuntu,
> operating with their funky VPN.
> On Thu, Feb 12, 2009 at 1:43 PM, Chad Whitacre <c...@zetaweb.com> wrote:
>> And are you running it on Windows? Or just hitting it from Windows in the
>> screenshots?
>> chad
>> LD 'Gus' Landis wrote:
>>> Yup, and from just a regular, unprivileged user account
>>> (of course, I can't use port 80, but 8080 is almost as
>>> well known).
>>> On Thu, Feb 12, 2009 at 12:39 PM, Chad Whitacre <c...@zetaweb.com> wrote:
>>>> This is great, Gus, thanks. So aspen works for you because it's pure
>>>> Python?
>>>> Easy to install in a "locked down" environment?
>>>> chad
>>>> LD 'Gus' Landis wrote:
>>>>> Chad,
>>>>> I have a gig at a major medical clinic supporting the
>>>>> primary laboratory system.
>>>>> The system is sort of "locked down" in that they don't
>>>>> want a lot of "other" stuff running there.
>>>>> I talked them into installing the IBM/AIX C compiler
>>>>> on a non-production box, and proceeded to build up
>>>>> a collection of tools: python, gnuplot, etc... and installed
>>>>> the executables on the production box.
>>>>> We collect data about the running application, # users,
>>>>> # transactions / 5 minute period, size of the various
>>>>> database tables, lots of stuff... then plot it to .png files.
>>>>> Aspen then provides the web server that lets the mgmt
>>>>> types look at the various graphs (which keeps them off
>>>>> of our backs and entertains them)... It has proven to be
>>>>> very helpful when having *those* discussions with the
>>>>> various system administrators and the SAN team....
>>>>> They'll start spinning some story, and so we just ask
>>>>> them how that relates to this or that graph... which means
>>>>> that we actually get some solutions to our complaints!
>>>>> Right now, the internal site is pretty static, but I am
>>>>> hoping to revamp it some over the next few months.
>>>>> Aspen is great for the simple things we have to do,
>>>>> and we haven't even done the cool stuff yet!
>>>>> Cheers,
>>>>> --ldl
>>>>> On Wed, Feb 11, 2009 at 11:46 AM, Chad Whitacre <c...@zetaweb.com>
>>>>> wrote:
>>>>>> Gus,
>>>>>> Definitely understand the $ issue, I'm experiencing that too. Haven't
>>>>>> even
>>>>>> started on Python 3 support for that very reason. :^/
>>>>>> The dev snapshots on zetadev.com are tracking trunk/, so they are up to
>>>>>> date, yes. When I get some docs written they'll show up there too;
>>>>>> likewise
>>>>>> with the point release.
>>>>>> Care to say anymore about how you're using aspen? It's always good to
>>>>>> hear
>>>>>> real-world use cases.
>>>>>> chad
>>>>>> LD 'Gus' Landis wrote:
>>>>>>> Chad,
>>>>>>> Listening and encouraged!
>>>>>>> I am disappointed in my level of effort helping on this,
>>>>>>> but earning $ has been in the way of that.
>>>>>>> Glad to see some movement on aspen, it is a nice
>>>>>>> tool and has been serving some internal needs well.
>>>>>>> I am planning to revamp the existing internal aspen
>>>>>>> site and will plan to move up to this new release.
>>>>>>> What is there is the version that I am currently
>>>>>>> running.
>>>>>>> So, where are you on moving to Python 3?
>>>>>>> Cheers,
>>>>>>> --ldl
>>>>>>> On Wed, Feb 11, 2009 at 6:59 AM, Chad Whitacre <c...@zetaweb.com>
>>>>>>> wrote:
>>>>>>>> Greetings,
>>>>>>>> Just in case anyone is listening, I just checked in a significant
>>>>>>>> changeset to the aspen trunk. I've folded the aspen.monitord
>>>>>>>> script into aspen itself. This means that the same infrastructure
>>>>>>>> used in development mode to restart the server when source files
>>>>>>>> change is now also used in production mode to restart the server
>>>>>>>> if/when the main (child) server process ever dies unexpectedly.
>>>>>>>> This update also includes logging configuration changes, as well
>>>>>>>> as tests for all changes. Once this update settles and I can
>>>>>>>> bring the documentation up to date, I plan to issue a point
>>>>>>>> release in the 0.8 line.
>>>>>>>> Thanks for listening. Would love any feedback on the latest changes.
|
