Coder Social home page Coder Social logo

elastic / ansible-elasticsearch Goto Github PK

View Code? Open in Web Editor NEW
1.6K 415.0 851.0 1.19 MB

Ansible playbook for Elasticsearch

License: Other

Ruby 49.05% Python 8.13% Makefile 1.97% Jinja 40.85%
ansible ansible-role elasticsearch role-elasticsearch

ansible-elasticsearch's People

Contributors

aevaonline avatar barryib avatar brad avatar branen avatar broferek avatar crazybus avatar cyrilleverrier avatar dcleric avatar dekhtyarev avatar elasticmachine avatar electrical avatar eradical avatar itsmed avatar jakommo avatar janderson2 avatar jeffrey-e avatar jmlrt avatar konasp avatar lde avatar meersjo avatar mgreau avatar nduytg avatar nkammah avatar nullkarma avatar pemontto avatar pixelrebel avatar qk4l avatar robin13 avatar slothofanarchy avatar veger avatar

Stargazers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

Watchers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

ansible-elasticsearch's Issues

cloud-aws plugin configuration

How do I add additional properties to:

es_plugins:
- plugin: elasticsearch-cloud-aws
version: 2.5.0

to match:

cloud:
aws:
access_key: *********
secret_key: **********
discovery:
type: ec2

Thanks,
Per

Unable to set java version

I've been testing the role with a few plugins that require java 8 (openjdk-8-jre-headless). Attempting to set the java: variable directly in the playbook, or in a separate vars file does not override the default. As a workaround, I can set it using the --extra-vars flag on runtime.

The use of include_vars: in tasks/main.yml is the culprit. According to https://github.com/ansible/ansible/issues/11807 , this is 'expected behaviour'.

Better Support for Plugin removal

Ansible role currently only adds plugins and does not support plugin removal.

First improvement will:

  1. Remove and re-install all plugins if ES is upgraded - as required in 2.x
  2. Provide aa flag to re-install all plugins
  3. Remove all plugins if none are specified and some are installed
  4. Install plugins listed and not installed - currently supported

More tricky, and separate ticket:

  1. Removal of plugins that are installed but not listed in the playbook. Requires additional logic as ES lists names differently than install names

udpate-rc.d fails on Ubuntu with multiple nodes on the same machine

/usr/sbin/update-rc.d fails on Ubuntu (15.04):

fatal: [hostname]: FAILED! => {"changed": false, "failed": true, "msg": "Error when trying to enable node2_elasticsearch: rc=1 Synchronizing state for node2_elasticsearch.service with sysvinit using update-rc.d...\nExecuting /usr/sbin/update-rc.d node2_elasticsearch defaults\ninsserv: script node2_elasticsearch: service elasticsearch already provided!\ninsserv: exiting now!\nupdate-rc.d: error: insserv rejected the script header\n"}

node2 is the es_instance_name.

I believe the issue is related to the following line in the debian init script:

# Provides:          elasticsearch

Should that be something like this?

# Provides:          {{es_instance_name}}_{{default_file | basename}}

My playbook looks like this:

- hosts: elasticsearch
  vars:
    es_major_version: "2.x"
    es_version: "2.2.0"
    es_heap_size: "31g"
    es_max_open_files: 262140
    es_data_dir: "/elasticsearch/data"
    es_log_dir: "/elasticsearch/log"
  roles:
    - { role: elasticsearch, es_instance_name: "node1", es_config: { node.name: "node1", http.port: 9200, transport.tcp.port: 9300, cluster.name: "cluster", bootstrap.mlockall: true, discovery.zen.ping.multicast.enabled: false } }
    - { role: elasticsearch, es_instance_name: "node2", es_config: { node.name: "node2", http.port: 9201, transport.tcp.port: 9301, discovery.zen.ping.unicast.hosts: "localhost:9300", cluster.name: "cluster", bootstrap.mlockall: true, discovery.zen.ping.multicast.enabled: false } }
    - { role: elasticsearch, es_instance_name: "node3", es_config: { node.name: "node3", http.port: 9202, transport.tcp.port: 9302, discovery.zen.ping.unicast.hosts: "localhost:9300", cluster.name: "cluster", bootstrap.mlockall: true, discovery.zen.ping.multicast.enabled: false } }

(I assume this is also an issue on redhat, but dont have a system to test.)

Multiple data_dir definitions does not work

Defining multiple data directories:

 es_data_dir: "/mnt/xvdb,/mnt/xvdc"

Results in

DATA_DIR=/mnt/xvdb,/mnt/xvdc/ec2_marvel-rclarke_marvel

The node name is pasted after the last directory.

I don't think it is necessary to have a separate directory for each node running on a single machine, same as it is not necessary to have a separate directory for logs or work I think...

Ubuntu 14.04 - elastic service cannot be stopped or restarted

On Ubuntu 14.04 you cannot restart (or stop) the elastic service with this command:

service <es_instance_name_elasticsearch> restart

Currently you have to restart the service, you have to kill the process and then use:

service <es_instance_name_elasticsearch> start

Allow for any plugin to be installed

Currently we are forcing people to be only able to install Elasticsearch plugins with --install elasticsearch/{{ item.plugin }}/{{ item.version }}
Could we please make this more open?
the item.plugin could be something like elasticsearch/marvel or an other author/pluginname combo.

Logrotate as part of ES Ansible setup

I just started using the ES Ansible playbook, and noticed that there aren't any logrotate entries.

Would be nice to see a logrotate file added for ES automatically as part of the playbook as I can't seem to find any reference to one.

Support plugin management for ES 1.x

Between ES 1.x and 2.x plugins management verbs changed.

  • ES 1.x: bin/plugin --install [plugin_name]
  • ES 2.x: bin/plugin install [plugin_name]

We should catch this change during the plugin installation and removal. At least, as long we support ES 1.x

How do you add custom scripts/templates?

The copy commands in the tasks/elasticsearch-scripts.yml and tasks/elasticsearch-templates.yml are pretty clear in their intent.

So, is the expectation that I should clone this repo, and add any custom scripts/templates to the appropriate directory in files/?

Is there a way to configure a playbook to reference a different directory to load scripts/templates from?

Check plugin directory before plugin install

Avoid automatic upgrades by checking directory before trying to install a plugin: if directory exists, then don't try to install again unless the reinstall variable is set.

Remember - the directory name is not necessarily the same as the plugin name

Plugins fail due to deleted /etc/default/elasticsearch

When using the role to manage plugins, it fails in consecutive runs due to deleted /etc/default/elasticsearch

The elasticsearch plugin command used in elasticsearch-plugins.yml to detect already installed plugins fails with

# ./plugin list
./plugin: 49: .: Can't open //etc/default/elasticsearch

The playbook fails with

"ERROR: plugin directory /usr/share/elasticsearch/plugins/sams/kopf already exists. To update the plugin, uninstall it first using 'remove kopf' command"

You delete /etc/default/elasticsearchin elasticsearch-config.yml.

Running Debian Jessie and elasticsearch 2.2.0

Install plugin by URI

Provide a path from which to install a plugin.
Add a uri parameter to each plugin definition like this

Advanced Cluster Management Features

Proposal to support:

  1. Full Cluster Stop cluster
  2. Stop/Start/Restart Specific Node
  3. Full Cluster Restart
  4. Rolling Restart

Some of the above could already be achieved. It may not be appropriate to include this functionality in the default role - we may wish to create a separate management role.

To be discussed.

Switch to apt / yum repo's

At the moment the code uses a download link.
Would be nice if we can use our official repositories instead.

plugin binary can't find elasticsearch defaults file on Ubuntu 14.04

I am using Ubuntu 14.04.

I am configuring Elasticsearch in a role like so:-

    - { role: elasticsearch,
              es_instance_name: "es01",
              es_heap_size: "3g",
              es_data_dirs: "/opt/app/elasticsearch/data",
              es_log_dir: "/opt/app/elasticsearch/logs",
              es_work_dir: "/opt/app/elasticsearch/temp",
              es_config: { network.host: '[ "_local_", "_docker0_" ]',
                           transport.host: '_eth0_',
                           http.port: 9200,
                           transport.tcp.port: 9300,
                           max-open-files: true,
                           bootstrap.mlockall: true,
                           script.inline: true,
                           script.indexed: true,
                           index.translog.durability: async,
                           index.queries.cache.everything: true } }

This leaves me with a defaults file at /etc/default/es01_elasticsearch.

This happens when I try to run the plugin command:-

root@my-es-host:/usr/share/elasticsearch# bin/plugin                                               โ”‚~
bin/plugin: 49: .: Can't open //etc/default/elasticsearch

I can fix it up manually by editing bin/plugin like so:-

ES_ENV_FILE="/etc/default/es01_elasticsearch"

Am I missing some configuration or is this a bug? Thanks for your help.

es_config usage fails to start elasticsearch

Every time I use the es_config parameter elasticsearch fails to start:

$ cat playbooks/elasticsearch.yml

---
- name: One Node Elasticsearch
  hosts: search
  become: True
  roles:
    - { role: ansiblebit.oracle-java, oracle_java_set_as_default: yes }
    - { role: elasticsearch, es_instance_name: "node1" , es_config: { network.host: "_global_" } }
  vars:

If I do NOT use es_config everything works fine.

Cleanup unused init, env configs and yml files

The rpm and deb packages install an elasticsearch.yml, env default file (e.g. /etc/sysconfig/elasticsearch) init script and systemd file. These are not used as the role creates its own copy for each node instance - delimiting them with the mandatory instance name.
This ticket proposes cleaning these files up on completion of install.

Create user if it doesn't exist

Currently the default user "elasticsearch" is used - this is installed by the package manager.
If installed through a manual URL this might not be the case. User may also wish to use another user.
Proposal is to create the user if it doesn't exist.

After installing, elasticsearch will not start due to no logging configuration?

I just did an initial test install with this role. I configured three nodes and ran the play. When I tried checking the health of the cluster, it became apparent that elasticsearch was not started.

So I tried starting it manually, and I got this:

root@node1:~# /usr/share/elasticsearch/bin/elasticsearch
Failed to configure logging...
ElasticsearchException[Failed to load logging configuration]; nested: NoSuchFileException[/usr/share/elasticsearch/config];
    at org.elasticsearch.common.logging.log4j.LogConfigurator.resolveConfig(LogConfigurator.java:158)
    at org.elasticsearch.common.logging.log4j.LogConfigurator.configure(LogConfigurator.java:103)
    at org.elasticsearch.bootstrap.Bootstrap.setupLogging(Bootstrap.java:204)
    at org.elasticsearch.bootstrap.Bootstrap.init(Bootstrap.java:258)
    at org.elasticsearch.bootstrap.Elasticsearch.main(Elasticsearch.java:35)
Caused by: java.nio.file.NoSuchFileException: /usr/share/elasticsearch/config
    at sun.nio.fs.UnixException.translateToIOException(UnixException.java:86)
    at sun.nio.fs.UnixException.rethrowAsIOException(UnixException.java:102)
    at sun.nio.fs.UnixException.rethrowAsIOException(UnixException.java:107)
    at sun.nio.fs.UnixFileAttributeViews$Basic.readAttributes(UnixFileAttributeViews.java:55)
    at sun.nio.fs.UnixFileSystemProvider.readAttributes(UnixFileSystemProvider.java:144)
    at sun.nio.fs.LinuxFileSystemProvider.readAttributes(LinuxFileSystemProvider.java:97)
    at java.nio.file.Files.readAttributes(Files.java:1686)
    at java.nio.file.FileTreeWalker.walk(FileTreeWalker.java:109)
    at java.nio.file.FileTreeWalker.walk(FileTreeWalker.java:69)
    at java.nio.file.Files.walkFileTree(Files.java:2602)
    at org.elasticsearch.common.logging.log4j.LogConfigurator.resolveConfig(LogConfigurator.java:142)
    ... 4 more
log4j:WARN No appenders could be found for logger (bootstrap).
log4j:WARN Please initialize the log4j system properly.
log4j:WARN See http://logging.apache.org/log4j/1.2/faq.html#noconfig for more info.
Exception in thread "main" java.lang.RuntimeException: don't run elasticsearch as root.
    at org.elasticsearch.bootstrap.Bootstrap.initializeNatives(Bootstrap.java:93)
    at org.elasticsearch.bootstrap.Bootstrap.setup(Bootstrap.java:144)
    at org.elasticsearch.bootstrap.Bootstrap.init(Bootstrap.java:285)
    at org.elasticsearch.bootstrap.Elasticsearch.main(Elasticsearch.java:35)
Refer to the log for complete error details.
root@node1:~# ls /etc/elasticsearch/
elasticsearch.yml  node1  logging.yml  scripts

Here are the ansible vars, just replace node1 with node2 or node3 to get the other nodes config:

es_version: 2.1.1
es_log_dir: "/opt/elasticsearch/logs"
es_work_dir: "/opt/elasticsearch/temp"
es_heap_size: "3072m"
es_config: 
  cluster.name: "asdfqwerty"
  discovery.zen.ping.unicast.hosts: "http://node1:9301"
  http.port: 9200
  transport.tcp.port: 9301
  bootstrap.mlockall: True
  discovery.zen.ping.multicast.enabled: False
  path.repo: "/path/to/repo/path"
  discovery.zen.minimum_master_nodes: 2
  action.destructive_requires_name: True

es_instance_name: "node1"

es_config: 
  node.name: "node1"
  node.data: True
  node.master: True

es_data_dir: "/mounts/node1"

Did I miss some required var?

I did try /etc/init.d/node1_elasticsearch start and it did not work, nor did it output any errors. Just Starting ... [OK]. /var/logs/elasticsearch is empty so I can't figure anything out from there.

So, what obvious step am I missing?

Should this kind of question be posted on discuss.elastic.co somewhere instead of here? If so, what forum?

Clearly Determine when Systemd is used vs Init

This is currently left to which ever takes precedence as to what the user configures post install i.e. both scripts are installed.
The proposal is we clearly delimitate which is used, why and when.
@electrical maybe we should replicate the puppet modules behaviour here?

Skip Java package install if java already installed

Hello

Could it be possible to check whether Java is already present before to install it through package manager?

In my case, Oracle JDK is installed through an ansible role that download the tgz directly from Oracle.
I would like to avoid openjdk installation if not required.

For example, changing java.yml to:

---
- name: Check Java
  shell: command -v java
    register: check_java
    ignore_errors: True
    changed_when: False

- name: RedHat - Ensure Java is installed
  yum: name={{ java }} state=latest
  when: ansible_os_family == 'RedHat' and check_java.rc > 0

- name: Debian - Ensure Java is installed
  apt: name={{ java }} state=present update_cache=yes force=yes
  when: ansible_os_family == 'Debian' and check_java.rc > 0

Best regards.

Geoff.

Debian 8 - Issue with Systemd

Currently Systemd results in an error and fails to work when tested in Docker. Further investigation required. Error to be added here.

Centos-7 fails with service

Not sure where the fault lays but should be found out :-)

       TASK: [elasticsearch | Start elasticsearch service] ***************************
       failed: [localhost] => {"failed": true}
       msg: failed determining service state, possible typo of service name?

       FATAL: all hosts have already failed -- aborting

Test run levels

Test run levels are correctly applied per OS. Given the challenge with testing (using Kitchen) that ES is restarted on machine reboot, this gives us a confidence this is behaving correctly.

Test Idempotent behaviour of Role

All current tests install to a clean docker image. The image is destroyed on completion of the test run. No tests currently confirm the behaviour if a role is applied multiple times to an image.

Whilst this is difficult to achieve with Kitchen tests, we could test the behaviour is correct when the role is applied to a docker image which already has nodes installed. This could be used to confirm:

  1. No changes are applied and the nodes are NOT restarted i.e. the role is Idempotent
  2. Changes are correctly applied and result in node restarts.

@electrical I propose choosing one platform on which to test this - in Kitchen it will require another platform/docker image preloaded with Elasticsearch. To avoid test explosion we might just limit to one platform therefore.

Remove Plugins that re installed but not listed in the playbook.

Currently if the user does the following:

  1. Installs ES with plugins
  2. Changes the plugins listed - adds and removed
  3. Re-runs the playbook

The plugins are not changed to those in step (2) - they are required to specify es_plugins_reinstall:true. My current proposal is to remove all plugins and re-install them in the event of ANY delta.

@jakommo thoughts?

Validate configuration

Using a map for configuring elasticsearch.yml is super flexible and nice, but it makes it very easy to miscreate configurations that will not start. It would be very nice if there was some sort of validation that checks syntax.

Allow specification of own user name

Allow the specification of a different username under which elasticsearch should be run. Currently we only support "elasticsearch".

I propose we do not create this user if it doesn't exist i.e. we assume its existence.

ERROR: plugin directory already exists (idempotence)

Issue: The plugin management is not idempotent (using current master, commit e14ebe0).

A plugin gets installed on first ansible-playbook run and causes "ERROR: plugin directory already exists" on the second run.

To be able to run a playbook multiple time, one has to workaround it by setting es_plugins_reinstall to true (default is false), but then the playbook reports changes on each run (not idempotent either).

Expected behaviour: second run finishes without error, with zero changes.

Environment: Fresh Ubuntu 14.04 64bit in Vagrant

Playbook (idemp.yml):

---
- name: Provision the ES node or cluster
  hosts: es
  remote_user: vagrant
  become: yes
  become_user: root
  gather_facts: true

  vars:
    es_plugins:
      - plugin: cloud-aws

  roles:
    - { role: elasticsearch, es_instance_name: "node1" }

First run:

marji@anna:~/projects/ansible-project-logstash$ ansible-playbook -i hosts idemp.yml 

--- cut ---

PLAY RECAP *********************************************************************
10.8.8.2                   : ok=47   changed=18   unreachable=0    failed=0   

Second run:

marji@anna:~/projects/ansible-project-logstash$ ansible-playbook -i hosts idemp.yml 

--- cut ---

TASK [elasticsearch : Remove elasticsearch plugins] ****************************
skipping: [10.8.8.2] => (item= cloud-aws) 

TASK [elasticsearch : Install elasticsearch plugins] ***************************
failed: [10.8.8.2] => (item={u'plugin': u'cloud-aws'}) => {"changed": false, "cmd": ["/usr/share/elasticsearch/bin/plugin", "install", "cloud-aws", "--silent"], "delta": "0:00:10.256230", "end": "2016-06-05 03:27:35.476620", "failed": true, "failed_when_result": true, "item": {"plugin": "cloud-aws"}, "rc": 74, "start": "2016-06-05 03:27:25.220390", "stderr": "", "stdout": "ERROR: plugin directory /usr/share/elasticsearch/plugins/node1/cloud-aws already exists. To update the plugin, uninstall it first using 'remove cloud-aws' command", "stdout_lines": ["ERROR: plugin directory /usr/share/elasticsearch/plugins/node1/cloud-aws already exists. To update the plugin, uninstall it first using 'remove cloud-aws' command"], "warnings": []}

PLAY RECAP *********************************************************************
10.8.8.2                   : ok=43   changed=0    unreachable=0    failed=1   

The error above is: "ERROR: plugin directory /usr/share/elasticsearch/plugins/node1/cloud-aws already exists. To update the plugin, uninstall it first using 'remove cloud-aws' command"

Debian-8 fails java package

   TASK: [elasticsearch | Debian - Add java repos] *******************************
   failed: [localhost] => (item=ppa:webupd8team/java) => {"failed": true, "item": "ppa:webupd8team/java"}
   msg: Invalid repository string: ppa:webupd8team/java

Package version pinning

When a specific version of Elasticsearch is defined, this will be pinned in the package manager so that an inadvertent apt-get upgrade will not upgrade to the latest elasticsearch.

Make Java Repo Configurable

Given the situation with default java versions on Centos and Debian based systems, users are likely to want to specify an external repo to supply Java e.g. for Oracle. Currently the role limits them to IcedTea distribution and the latest version available through the default repos.

data_dirs environment wrongly expanded

Somehow this showed up after running the playbook in the /etc/system/multi-user.target.wants/node1_elasticsearch.service file

Environment=DATA_DIR=[,',/,v,a,r,/,l,i,b,/,e,l,a,s,t,i,c,s,e,a,r,c,h,/,e,s,-,0,1,-,n,o,d,e,1,',]

Also shows in /etc/elasticsearch/node1/elasticsearch.yml
path.data: [,',/,v,a,r,/,l,i,b,/,e,l,a,s,t,i,c,s,e,a,r,c,h,/,e,s,-,0,1,-,n,o,d,e,1,',]

Expect :

Template

[Service]
Environment=ES_HOME={{es_home}}
Environment=CONF_DIR={{conf_dir}}
Environment=DATA_DIR={{ data_dirs | array_to_str }}
Environment=LOG_DIR={{log_dir}}
Environment=PID_DIR={{pid_dir}}
EnvironmentFile=-{{instance_default_file}}

Add shield support

I would like to add shield support, and I was wondering how we can structure things like variables and templates.

Here are my proposals:

Dicts structure:

es_license: my_vaulted_private_and_secret_license
es_users:
  - user: bob
    password: my_vaulted_secret_password
    role: user

es_role_mapping:
  - admin:
      - "cn=admins,dc=example,dc=com"
  - user:
      - "cn=users,dc=example,dc=com"
      - "cn=other-users,dc=example,dc=com"

or this structure (I personally prefer this one):

es_license: my_vaulted_private_and_secret_license
es_shield:
  - users:
      - user: bob
        password: my_vaulted_secret_password
        role: user
  - role_mapping:
      - admin:
        - "cn=admins,dc=example,dc=com"
      - user:
        - "cn=users,dc=example,dc=com"
        - "cn=other-users,dc=example,dc=com"

Templates structure:

Add these following templates to configure shield's roles and role mappings. For the main configuration, we'll use the es_config object.

+-- templates
|   +-- ...
|   +-- shield
|   |  +-- role_mapping.yml.j2
|   |  +-- roles.yml.j2

Do you have any suggestion or preference on how we should add this feature?

Custom Repos for Elasticsearch install

Currently installs can be only installed from the official Elastic repos. We commonly encounter users who have systems with no external internet access, instead hosting their own yum/apt-get repos. This feature would allow users to specify the repo as a parameter - if specified this would be used for the install.

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    ๐Ÿ–– Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. ๐Ÿ“Š๐Ÿ“ˆ๐ŸŽ‰

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google โค๏ธ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.