Skip to main content

Amazon.com rebates

Then there is the rebates. As I mentioned in my last post that Amazon computed the rebate price even though the "purchase by" period has passed... Now here is some more Amazon magic.

As I was still looking for a good barebones computer for some clustering I wanted to experiment with I found another MSI device. This one appears to be $32 after rebate(s). That seems to be a great price if you ask me!


So when I looked at the rebate links I was not surprised to see that while the dates were ok... there were 2 rebates in the popup. So clearly someone made a mistake. Whether it was Amazon or MSI it's tough to tell but he rebates are identical and I seriously doubt that MSI is going to accept two rebates for the same purchase.

While this was not the compete terms and conditions (there was some small print at the bottom) This section looked familiar to many other rebates I've seen. The good news is that it's not limited to one per household and not even one per purchase.

Well, I was wrong again. When I read the fine print I found:
Limit (1) rebate per qualifying rebate offer, per person, billing address, company, household and receipt/invoice/packing slip during the eligibility period, except were prohibited by law.
I don't think this was intentionally misleading and in some cases rebates can make the difference. Keep in mind that rebates are the company's attempt to capture analytics that would otherwise be limited to the seller. While that makes sense on one device it would drive the margins down too far and encourage resale competition on eBay etc.

Finally, the UPC and the application need to be postmarked no later than 15 days from purchase. Since I previously noted that in some cases there was a 20 to 45 day delay it might be impossible to collect.

Popular posts from this blog

Prometheus vs Bosun

In conclusion... while Bosun(B) is still not the ideal monitoring system neither is Prometheus(P).

TL;DR;

I am running Bosun in a Docker container hosted on CoreOS. Fleet service/unit files keep it running. However in once case I have experienced at least one severe crash as a result of a disk full condition. That it is implemented as part golang, java and python is an annoyance. The MIT license is about the only good thing.

I am trying to integrate Prometheus into my pipeline but losing steam fast. The Prometheus design seems to desire that you integrate your own cache inside your application and then allow the server to scrape the data, however, if the interval between scrapes is shorter than the longest transient session of your application then you need a gateway. A place to shuttle your data that will be a little more persistent.

(1) storing the data in my application might get me started more quickly
(2) getting the server to pull the data might be more secure
(3) using a push g…

Entry level cost for CoreOS+Tectonic

CoreOS and Tectonic start their pricing at 10 servers. Managed CoreOS starts at $1000 per month for those first 10 servers and Tectonic is $5000 for the same 10 servers. Annualized that is $85K or at least one employee depending on your market. As a single employee company I'd rather hire the employee. Specially since I only have 3 servers.

The pricing is biased toward the largest servers with the largest capacities; my dual core 32GB i5 IntelNuc can never be mistaken for a 96-CPU dual or quad core DELL

If CoreOS does not figure out a different barrier of entry they are going to follow the Borland path to obscurity.

Weave vs Flannel

While Weave and Flannel have some features in common weave includes DNS for service discovery and a wrapper process for capturing that info. In order to get some parity you'd need to add a DNS service like SkyDNS and then write your own script to weave the two together.
In Weave your fleet file might have some of this:
[Service] . . . ExecStartPre=/opt/bin/weave run --net=host --name bob ncx/bob ExecStart=/usr/bin/docker attach bob
In sky + flannel it might look like:
[Service] . . . ExecStartPre=docker run -d --net=host --name bob ncx/bob ExecStartPre=etcdctl set /skydns/local/ncx/bob '{"host":"`docker inspect --format '{{ .NetworkSettings.IPAddress }}' bob`","port":8080}' ExecStart=/usr/bin/docker attach bob
I'd like it to look like this:
[Service] . . . ExecStartPre=skyrun --net=host --name bob ncx/bob ExecStart=/usr/bin/docker attach bob
That's the intent anyway. I'm not sure the exact commands will work and that's partly why we…