Despite the movement to cloud, data centers will still be around for the foreseeable future.
Virtualizing the data center may make it more efficient and agile but additional processing power may be needed.
If the public cloud computing market were our solar system, then Amazon Web Services would be Jupiter and Saturn together and the remaining five fast-growing big clouds would be like the inner planets like Mercury, Venus, Earth, Mars, and that pile of rocks that used to be a planet mixed up with those clouds that are finding growth a bit more challenging – think Uranus and Neptune and maybe even Pluto if you still want to count it a planet.
This analogy came to us in the wake of Amazon’s reporting of its financial results for the first quarter of …
The Datacenter Does Not Revolve Around AWS, Despite Its Gravity was written by Timothy Prickett Morgan at The Next Platform.
Coinciding (roughly) with the version 2.2 release of StackStorm, the Ghost2logger pack has been released.
This pack provides in essence a “Syslog sensor” that provides the user a tuple match on a Syslog entry, tuples in this case being:
The actions can then be anything you so desire, either triggering a sinlge action or full blown workflow with Mistral or Cloudslang.
In terms of using the pack, all that is required from the user is the creation of rules and pointing your syslog source to the Ghost2logger location. Most of the time Ghost2logger will live on the same install as StackStorm, so point it at the IP address StackStorm resides. Worried abut StackStorm load? Don’t be. Syslogs aren’t actually processed by StackStorm, but are processed by the Ghost2logger binary. Only matched entries dispatch triggers. There is some inception going on here. Prepare yourself for this: “Rules will only match what the rules have created the match conditions for”. If you understand this hypothesis correctly, you will understand that this is simple feedback from the rules base back to Ghost2logger.
The pack itself consists of a number Continue reading