noobaa / noobaa-core

Object-storage Transformer server for Node.js 🦾🤖🦾 (s3 => file / s3 / azure / google / erasure-code / tiering / merge / cache / logging / replicate / custom...)

---

NooBaa is a data service for cloud environments, providing S3 object-store interface with flexible tiering, mirroring, and spread placement policies, over any storage resource that allows GET/PUT including S3, GCS, Azure Blob, Filesystems, etc.

NooBaa simplifies data administration by connecting to any of the storage silos from private or public clouds, and providing a single scalable data service, using the same S3 API and management tools. NooBaa allows full control over data placement, letting you place data based on security, strategy and cost considerations, in the granularity of an application.

---

Deploy to Kubernetes

To deploy NooBaa, we recommend using NooBaa CLI. Follow the instructions in https://github.com/noobaa/noobaa-operator#noobaa-operator

Once NooBaa CLI installed, simply Install the operator and noobaa with:

./noobaa install

The install output includes S3 service endpoint and credentials, as well as web management console address with credentials.

Getting this information is always available with:

./noobaa status

Remove NooBaa deployment can be done with:

./noobaa uninstall

Tutorial

(Click the image or the link to open the noobaa install demo on YouTube)

Help

• Website
• Wiki - articles for hackers
• Docs - the new docs site is almost ready...

Communicate

• [email protected]
• Subscribe to newsletter

Contribute

• How to Contribute
• Developers Guide

License

Apache License 2.0, see LICENSE

noobaa-core's Issues

Upload progress opacity is invalid

Streaming vs downloading and playing

1. Small files (under 10MB) should be downloaded and played.
2. Larger files should behave as follows:
   1. If the file is not streamable/previewable download it.
   2. If there is a configured REST server, stream/preview via the REST server.
   3. In all other cases, download.

files parts - we show undefined instead of port (need to remove ':undefined')

https://noobaa-alpha.herokuapp.com/console/bucket/files/E_TheRidge_6056425.webm#parts&page=1

Agent token should be taken from conf to avoid keeping user+password

also for s3 rest.

upload file name should be like original file, or add 1, 2, 3, suffix

today we always add a timestamp which is ugly.
we should try to use the original name first, and only if taken to find the next empty sequence number.

After a replication failure, we fail the upload instead of write the chunk again (from the client)

After we upload the first chunk, we need to replicate it.

Replications may fail, and we should try to upload the first chunk again to another node.

File listed blocks have and IP an undefined port

disconnecting from signalling server cause 100% cpu

simply start an agent and disconnect from the network

The result is a massive amount of messages like this and 100% cpu

INFO:socket_host_udp.cc(298)] sendto() has failed twice returning a transient error. Dropping the packet

Agnet installation is too big and creates too many files

chrome warns on downloading the agent exe

Agnet installer exe properties are missing

When viewing the file properties in windows, the Properties tab is empty.
Here is a GOOD example.

A system with 8 offline nodes showed 0 nodes on overview but map showed points.

Date: 11/3/2015 09:00 IL time.
System: https://noobaa-alpha.herokuapp.com

The system only had 8 nodes at the time I looked at it - all of them offline.
The weirdness was in the fact that the nodes number showed only the live nodes but the map showed all the nodes.

Suggest to modify the front screen to include all the nodes and an indication on the live ones.

Upload progress needs to provide some progress indication for short term progress

Currently there is the purple line.
If the file is big, you'd look at a static line and have no clue something is going on.
Need KB/s or something that moves all the time.

avoid replicate to self

Add node installer link (signed url from S3 bucket)

same for rest installer.
s3 path per system.

Node OS storage space is not real

display failed upload as failed (currently showing progress)

A file that did not "recieive" new parts for 5min (???) should be marked as failed upload.

activity log - log when node becomes offline

Timeout along the upload path are not aligned

We have write retries, browser timeout, replicates retries and timeout - non are aligned, so we keep fail the upload even if we can handle it.

Monitor and notify on file health

Files with missing/faulty parts should be indicated accordingly.
Faulty files should be notified but not downloaded.

10 replicates on three nodes creates "overload"

We see that sending "many" (3) requests from one node to another at the same time - causes slow webrtc write on the buffer and ends with timeouts.

signalling should move to wss

UI file/node parts paging doesn't have knowledge on number of pages

sometimes replicate fails but upload report success

problem writing to activity log on node.create

TypeError: Cannot read property 'name' of undefined
at transformer.js:149
at arrayFilter (tv4.js:994)
at Function.filter (nb_api.js:290)
at transformer.js:149
at angular.js:13189
at l.$get.l.$eval (angular.js:14401)
at l.$get.l.$digest (angular.js:14217)
at angular.js:14440
at e (angular.js:4905)
at angular.js:5285
transformer.js:149 RELOAD SYSTEM FAILED TypeError: Cannot read property 'name' of undefined {stack: "TypeError: Cannot read property 'name' of undefine…/ajax/libs/angularjs/1.3.14/angular.min.js:44:112", message: "Cannot read property 'name' of undefined"}message: "Cannot read property 'name' of undefined"stack: "TypeError: Cannot read property 'name' of undefined↵ at http://127.0.0.1:5001/public/js/index.js:90943:64↵ at arrayFilter (http://127.0.0.1:5001/public/js/index.js:67847:13)↵ at Function.filter (http://127.0.0.1:5001/public/js/index.js:72070:14)↵ at http://127.0.0.1:5001/public/js/index.js:90928:45↵ at http://ajax.googleapis.com/ajax/libs/angularjs/1.3.14/angular.min.js:112:20↵ at l.$get.l.$eval (http://ajax.googleapis.com/ajax/libs/angularjs/1.3.14/angular.min.js:125:305)↵ at l.$get.l.$digest (http://ajax.googleapis.com/ajax/libs/angularjs/1.3.14/angular.min.js:122:398)↵ at http://ajax.googleapis.com/ajax/libs/angularjs/1.3.14/angular.min.js:125:392↵ at e (http://ajax.googleapis.com/ajax/libs/angularjs/1.3.14/angular.min.js:40:74)↵ at http://ajax.googleapis.com/ajax/libs/angularjs/1.3.14/angular.min.js:44:112"get stack: function () { [native code] }set stack: function () { [native code] }proto: Errortransformer.js:149 (anonymous function)angular.js:13189 (anonymous function)angular.js:14401 $get.l.$evalangular.js:14217 $get.l.$digestangular.js:14440 (anonymous function)angular.js:4905 eangular.js:5285 (anonymous function)

in nb_api.js upon

case 'node.create':
l.category = 'nodes';
l.text = 'Added node ' + l.node.name;
break;

Deleting a file does not delete parts allocated on the nodes 

See also: #57
Probably same RCA

Race: delete_object_mapping & allocate_object_parts

A race can occur between delete object mappings and allocate object parts. In a case of a chunk which is about to be deleted, but equals in hash to a chunk being uploaded, we might use that chunk in the allocation but then delete it..

We can either protect it by locking the specific chunk, or by marking it as delete pending and waiting for the deletion for some interval (checking in the allocate if the chunk is not delete pending).
Choosing the second solution we should be careful to return the RPC context and not block it on the deletion pend.

Specific node - Self test not clear enough

Perhaps change to Connectivity test, with tool tip to explain that this is a connectivity test from this node to all others.

User facing events should be issued via a framwork

Currently some events are issued to the event log.
Some issues pop up a red error message.
Some don't show anything.

Suggestion:
To force all messages to be issued vie a single framework that will get an input and will be responsible to propagate to the right place/s.

Upon upload, dedupe only with available chunks

None available chunks should be fixed

gui calls http://localhost/' directly, should not assume this, plus https not handled

Mixed Content: The page at 'https://noobaa-alpha.herokuapp.com/console/overview' was loaded over HTTPS, but requested an insecure XMLHttpRequest endpoint 'http://localhost/'. This request has been blocked; the content must be served over HTTPS.

Not all DB queries handle the deleted != NULL situations

Currently our DB objects are not really deleted, merely marked as deleted.
In several of our queries we don't verify if the objects we received are marked as deleted (or don't filter non deleted).

We should fix this flows as they will cause us to crash.

Files Screen - Search for file name with * char

We should either prevent * in the filter, or take it into consideration.
Currently searching for D*B yields results such as
P_BMX_6058113.webm
...

File parts should show UP to 3 OK parts. All the rest should be hidden

on node creation we don't always get peer id from web server

as we cant identify ourselves to the signaling server, the agent cant work

Agent starting while web server or signal i down should not get stuck

currently seems that Atom prevents it from exiting, and it just hangs after failing to do Agent.start()

Pages that show multiple links and icons are noisy.

Test Date: 11/3/2015 09:00 IL timezone
Test System: https://noobaa-alpha.herokuapp.com

RPC retries should only apply on transient errors and not persistent errors

currently we don't differentiate the two types of errors, so the RPC code doesn't have the information, so we should decide on a clear separation of errors for transient vs. persistent.

transient errors could be - network issue, resource temporarily unavailable (DB, REDIS, HEROKU).

with ICE with multiplexing we should send back an indication of in-progress for requests we are processing, so that we won't retry and just add more pressure.

File parts should be tabular

Currently expected 3 in a line (based on string length for alignment).
Result is not aligned. Need to align all lines (including sublines)

After deletion of an object we still check for dedup and don't upload (DB still contains the deleted chunks)

CSS of text color gets crazy after some clicks and toggles black/white

also buttons text should be mostly white

Node/Tier/System storage space should take potential space

Closing tab/win while Upload/download in process should warn

windows agent_storage folder is not hidden and has "everyone permission"

need to hide and set permissions to admin only

Support Page - system button has no feedback

the system button (NESS) has no feedback once pressed (processing animation, then returns to normal).

Need to certify all installed packages (agent, streamer, s3, core etc).

Test Date: 11/3/2015 09:00 IL timezone

This bug was initiated by the lack of certification of the agent.

UI Breadcrumbs issue

Breadcrumbs-
*When entering a list (nodes list for example) there should be a way back (should add breadcrumb - nodes/ nodes list and/or add a back option). same issue on other lists.
*If "system"="overview" we should write overview/ home on bread crumbs

• The Resources page is a little confusing since the user presses "nodes" on the menu but suddenly there is another step on the breadcrumb (System / Resources /Nodes). Same thing on files.

activity log error on obj.uploaded

case 'obj.uploaded':
l.category = 'files';
l.text = 'Upload completed ' + l.obj.key;
break;

i.obj is undefined:

TypeError: Cannot read property 'key' of undefined
at transformer.js:149
at arrayFilter (tv4.js:965)
at Function.filter (nb_api.js:231)
at transformer.js:149
at angular.js:13189
at l.$get.l.$eval (angular.js:14401)
at l.$get.l.$digest (angular.js:14217)
at angular.js:14440
at e (angular.js:4905)
at angular.js:5285

RELOAD SYSTEM FAILED TypeError: Cannot read property 'key' of undefined {stack: (...), message: "Cannot read property 'key' of undefined"

Rename tasks and windows services

Suggestions:
Service: NooBaa_device_manager
nssm.exe: NooBaa_Agnet_wd
node.exe: NooBaa_Agnet

Severity 3
This can include documentation which was incomplete or incorrect, making it difficult to know how to use a task.

Interactive installation should provide some feedback

I installed the agent manually.
After I doubleclicked it in the windows explorer I got only a single indication - the windows certificate issue.
After it's done - no success/failure indication.

Severity explanation:
Severity 3
The task that you were attempting to use behaved in a manner which is incorrect and/or unexpected, or presented misleading or confusing information.