#datastores

[vmtek]

The number of vSphere HA heartbeat datastores for this host is 1 or 0, which is less than required: 2

{Blog} The number of vSphere HA heartbeat datastores for this host is 1 or 0, which is less than required: 2 #homelab

When building the lab environment you may only want to have the 1 Datastore setup.  If so you may encounter the above Warning

(more…)

View On WordPress

[ugureren90]

Yetecek mi bilmiyorum ama yedeklenecek biraz veriniz var. #radore #datacenter #server #servers #datastore #datastores #flyfiber #wicomtr (Radore)

[attackio]

keigai, MongoDB and missing records

I recently started on a product that uses my javascript stack (keigai/turtle.io/tenso), and MongoDB for persistent data storage. It's pretty light weight overall, and is geared around O(1) lookups, so finding data is fast... when it can be found. I setup a brand new server on DigitalOcean, running Ubuntu 14.04, the latest stable node (from their PPA), and the supplied MongoDB package. Everything went smoothly, and my code was deployed and running in minutes; fantastic! Yesterday I went to demo the API to a coworker, and my authentication didn't work. "Hmm, that's odd" I thought, assuming I had forgotten my password, or had a typo when I created the account, so I just made another... and created a bunch of related entities to demo pagination from tenso. Today I went to use that new account, and all the related entities were missing. "Hmmm" I thought. I SSH'd into the VPS, went into MongoDB via the CLI, and discovered all the _id fields had internal ObjectID values, instead of the v1 UUIDs assigned from my app. "Hmmm" I thought. I compared the versions of MongoDB (2.4.9 from Ubuntu, 2.6.4 from brew), checked the change log for MongoDB, and simply purged the repo supplied version and retrieved the latest stable version from 10gen. It turns out that 2.4.x (and probably earlier) has an issue with upsert commands that supply the _id, the fact that it wasn't changing was irrelevant, MongoDB was going to assign it's own IDs and that was that. Thankfully, installing 2.6.5 sorted everything out. The UUIDs my code creates & sets on the keigai records persisted to MongoDB properly, and suddenly I no longer had many duplicate versions of 'records' in various states, I had a precise data set! Total time to investigate and fix the problem: 5 minutes.

[datajournalismlinks]

Where do journalists post their data? It’s a pretty core tenet of open journalism that you share your sources; i.e. , you write a story about data then you make numbers available to download. So where is the data?

[attackio]

keigai, the data store library you've always wanted

Keigai is a data store library that has a super simple API, allowing it to work on the server or in a browser. It provides data stores, and two types of UI components: data lists & data grids, both of which can have an optional data filter input field (supports wildcards). Why would you want to use it? It's not opinionated, and it doesn't care what architecture you prefer. It works with everything! OOP, MVC, FP, etc., it just doesn't matter. You can program how you want, and keigai will handle the data modelling & visual reps for you. For external hooks, pub/sub (observer) is used. This allows you create reactive behavior with minimal effort. Keigai will also handle API abstraction automatically for you, by returning Deferreds from methods that "go over the wire" or use web workers for concurrent operations. Keigai could be considered the offspring of abaaso, or maybe it's evolutionary counter part; it is a fork of the code base. Instead of trying to be the 'everything' a web/node developer might want, keigai focuses on only one important need, the data model. Keigai is still in it's infancy, and is not usable today. I hope to have 0.2.0 released on npm & github in the coming weeks. More details can be found here.

[josh-atwell]

How do you size ISO Template Datastore?

While studying for my VCAP-DCD exam I came across a statement in the vSphere 4 design workshop student manual that had me chuckle.  To paraphrase:

There is no need for datastore overhead because templates do not run, and therefore do not have snapshots.

I have to say that I am split on this one because while templates do not have snapshots I ALWAYS provide at least 10% of free space in my Template datastores.

Let's break this down a bit.

I always design my environments with centralized datastores specifically for holding templates, ISOs, and occasional .flp files.

I try to keep the number of these datastores as low as possible based on the needs of the environment [Production/Dev/QA/Etc.]

Usually set this between 300-500 GB depending on how many OS's the environment needs to deploy.  Naturally this could be smaller in most environments.

I always leave at least 10-20% free on these datastores because I know we'll need to add new ISOs for new applications, new templates for new OSes or applications, and to update templates.

I have used the templates datastore as a staging drive in the past when resources were tight or having to wait for storage to be provisioned for new systems.

Wait, did you catch that?  The important one that VMware missed?  Yea, number 4. UPDATE TEMPLATES

I don't know about you but I love snapshots!  I love the fact that I can start a snapshot on a VM, run updates, see how it goes, and revert if it goes poorly.  Because of this I nearly ALWAYS convert my templates to VMs and initiate a snapshot before performing any updates.  This saves huge disk space that can be consumed by template clones that many organizations use to maintain consistency. 

In situations where I'm looking at large Service Pack differences I will typically make a clone of an existing template and perform the SP upgrade on the clone to get it up to date.  Even then I perform a snapshot first so that if there is an issue or failure I can simply revert back and try again.

Granted, most snapshots consume very little drive space but I have found that performing monthly or quarterly Windows updates on templates means 500MB+ writes.  Spread that over a half dozen VMs and now you're getting into several GB of snapshot space being consumed.  Other application updates will also initiate writes that would be written to the snapshot but those usually have very low impacts in my experiences.

All in all the amount of free space you would need to DESIGN for depends on the number of Templates you are updating, how many you perform simultaneously, and what operating systems you are updating.  These are things you'll need to communicate with your customer/team when planning the environment.

So yes VMware, I can not perform snapshots on a template, but when I update that template I want to make sure I designed my datastore so that there is enough resources for me to use snapshots for the purpose they were intended.  Just sayin' :)

Now. How do YOU design your Template Datastore?

[coderspiel]

In this talk we will cover everything from Riak's Dynamo legacy to it's embedded JavaScript interpreter and customizable backends. Not content to live purely in the theoretical, we will review a demo app using node.js to talk to Riak over http.

Adding Riak to your NoSQL Bag of Tricks - NoSQL NYC

[coderspiel]