Isn't it your job to do QA?
If you favor stability why would you do 'svn up' on a production element? :)
Job
Stefan Milo stefan@zendata.dk wrote:
A tool like observium is often used by people in Operations. People in Operations tend to favor stability over new features. The old if it's not broken mantra...
I would hate it if i updated Observium, and because of Toms fat fingers, didn't receive alerts if a critical interface went down.
I'm not saying theres anything wrong with the way you roll out updates. I'm just saying there might be a conflict of interest from you as a developer, and your target audience in Operations.
On a sidenote... Would it be possible to implement a feature that would alert you if you were trying to update a really old install? Something like "Error; you are trying to update from R3193 to R4203. Please update to R4100 before proceeding."
BR
Stefan Milo ________________________________________ Fra: observium [observium-bounces@observium.org] På vegne af Adam Armstrong [adama@memetic.org] Sendt: 1. august 2013 15:29 Til: Observium Network Observation System Emne: Re: [Observium] Pages Missing CSS
Tom fat-fingered some updates last night which broke css-from-relative-paths loading.
Usually when that kind of thing happens, it gets fixed a few minutes later, so you can just "svn up".
Observium doesn't really have releases, we operate a bit more like Arch Linux in that we have a rolling svn-based release system.
This means that when bad code goes out in an update, it's usually fixed before more than a couple of people notice. It also means you can (and should, updating between very different versions might break) update pretty frequently. We usually recommend once a week or so, but a lot of our users update whenever there's an svn change.
It's a little counter-intuitive to some people, as most people have been trained to update once every 6 months.
adam.
On 2013-08-01 11:08, Steve Nelson wrote:
Hi All
I have now managed to at least get a build of Observium and also added a couple of test devices to poll. All seems well apart from one issue.
All pages (apart from the initial index page) are appearing as if they had no CSS applied to them, also at the foor of each page I am seeing some mysql output which I am not sure should be there, items like :
Time 0.005s MySQL Cell 0/0s Row 11/0.001s Rows 6/0s Column 0/0s Memory Cached 34.7kB Page 5.86MB Peak 6.14MB
Any advice on getting the pages back on track would be great.
Cheers
Steve
Steve Nelson 10Yr CCIE#10055, OSCP#3725 Senior Network Engineer steve.nelson@calibre-secured.net
Telephone : 0845 5576355 Direct Line : 0191 6542060 Mobile : 07702247286
observium mailing list observium@observium.org http://postman.memetic.org/cgi-bin/mailman/listinfo/observium
_______________________________________________ observium mailing list observium@observium.org http://postman.memetic.org/cgi-bin/mailman/listinfo/observium _______________________________________________ observium mailing list observium@observium.org http://postman.memetic.org/cgi-bin/mailman/listinfo/observium