├── .gitignore
├── CONTRIBUTING.md
├── Dockerfile
├── Gemfile
├── Gemfile.lock
├── Makefile
├── README.md
├── _config.yml
├── _includes
    ├── custom
    │   ├── category_feed.xml
    │   └── category_json.json
    ├── footer.html
    ├── head.html
    └── header.html
├── _layouts
    ├── category_index.html
    ├── default.html
    ├── home.html
    ├── page.html
    ├── post.html
    ├── redirected.html
    └── root.html
├── _plugins
    ├── generate_categories.rb
    └── octopress_filters.rb
├── attachments
    ├── 2016-06-23-linux-and-skylake
    │   ├── config-4.4.0-generic
    │   └── config-4.4.0-lowlatency
    └── Special_Conditions_Betatest_OVH-COM.pdf
├── en
    ├── _posts
    │   ├── 2014-04-14-how-to-deploy-core-os-on-runabove.markdown
    │   ├── 2014-04-17-how-to-create-a-compute-instance-in-few-seconds.markdown
    │   ├── 2014-04-17-spinning-up-instances-with-saltstack.markdown
    │   ├── 2014-04-22-how-to-store-your-backup-with-duplicity-and-openstack-swift.markdown
    │   ├── 2014-04-22-how-to-use-cyberduck-with-openstack-swift.markdown
    │   ├── 2014-04-22-how-to-use-vagrant-with-openstack.markdown
    │   ├── 2014-05-13--how-to-optimize-upload-with-openstack-swift.markdown
    │   ├── 2014-05-15-how-to-install-an-orchestration-tool-juju.markdown
    │   ├── 2014-05-16-how-to-create-a-custom-image-for-runabove.markdown
    │   ├── 2014-05-16-how-to-create-a-windows-instance.markdown
    │   ├── 2014-05-19-import-a-custom-image-in-your-runabove-account.markdown
    │   ├── 2014-05-20-how-to-configure-remote-desktop-on-windows-server.markdown
    │   ├── 2014-05-20-how-to-use-runabove-api.markdown
    │   ├── 2014-05-28-Sharing-an-object-with-temp-url-system.markdown
    │   ├── 2014-05-29-how-to-deploy-dokku-on-runabove.markdown
    │   ├── 2014-06-17-how-to-install-docker-on-runabove.markdown
    │   ├── 2014-06-18-upload-your-first-object-inside-swift.markdown
    │   ├── 2014-07-07-how-to-configure-owncloud-7-with-swift.markdown
    │   ├── 2014-07-09-what-is-object-storage.markdown
    │   ├── 2014-07-28-deploy-load-balanced-wordpress.markdown
    │   ├── 2014-09-09-how-to-check-file-consistency-using-etag-and-md5.markdown
    │   ├── 2014-09-09-how-to-schedule-deletion-of-objects.markdown
    │   ├── 2014-09-22-create-private-network.markdown
    │   ├── 2014-09-24-foreman-openstack-multi-region.markdown
    │   ├── 2014-09-25-use-openstack-command-line-tools.markdown
    │   ├── 2014-09-26-update-bash-shellshock.markdown
    │   ├── 2014-10-01-create-ssh-keys.markdown
    │   ├── 2014-10-06-power8-features.markdown
    │   ├── 2014-10-13-how-to-install-jenkins-on-runabove.markdown
    │   ├── 2014-10-14-how-to-relay-postfix-mails-via-smtp.gmail.com-on-ubuntu-14.04.markdown
    │   ├── 2014-10-16-how-to-fix-sslv3-poodle-vulnerability-nginx-apache-on-ubuntu-14.04.markdown
    │   ├── 2014-10-16-how-to-install-gitlab.md
    │   ├── 2014-10-21-how-to-install-the-codebox-ide.md
    │   ├── 2014-10-28-how-to-set-up-an-ipv6-tunnel-on-ubuntu-14.04.markdown
    │   ├── 2014-11-07-private-network-nat.markdown
    │   ├── 2014-11-10-manage-instances-from-command-line-using-nova.markdown
    │   ├── 2014-11-17-send-reliable-emails-from-your-runabove-instance-with-mailjet.markdown
    │   ├── 2014-12-05-how-to-deploy-a-shipyard-cluster-on-runabove.md
    │   ├── 2014-12-12-docker-in-5-minutes-on-runabove-with-docker-machine.markdown
    │   ├── 2014-12-19-how-to-distribute-static-content-with-object-storage.md
    │   ├── 2014-12-19-how-to-put-object-storage-behind-your-domain-name.md
    │   ├── 2014-12-29-security-groups.md
    │   ├── 2014-12-30-ansible.md
    │   ├── 2015-01-29-attach-volume.md
    │   ├── 2015-02-07-how-to-use-S3QL-with-runabove.markdown
    │   ├── 2015-02-14-how-to-run-bottle-uwsgi-nginx.markdown
    │   ├── 2015-03-12-jekyll-and-swift-object-storage.md
    │   ├── 2015-08-10-how-to-get-data-from-runabove-iot.markdown
    │   ├── 2015-08-10-how-to-manage-iot-applications-using-runabove-api.markdown
    │   ├── 2015-08-10-how-to-manage-iot-applications-using-runabove-manager.markdown
    │   ├── 2015-08-10-how-to-push-data-to-runabove-iot.markdown
    │   ├── 2015-08-24-how-to-sync-runabove-object-storage-containers-to-ovh-public-cloud.markdown
    │   ├── 2015-10-13-how-to-use-arm-lab.markdown
    │   ├── 2015-10-13-how-to-use-vps-hdd-lab.markdown
    │   ├── 2015-10-16-how-to-serial-console-arm-instance.md
    │   ├── 2015-11-28-migrate-from-runabove-to-public-cloud.markdown
    │   ├── 2015-11-28-transfer-instance-backup-from-one-datacenter-to-another.markdown
    │   ├── 2015-11-28-transfer-volume-backup-from-one-datacenter-to-another.markdown
    │   ├── 2015-12-08-how-to-connect-an-agent.md
    │   ├── 2015-12-08-how-to-use-hiera.md
    │   ├── 2015-12-08-start-puppet-master-api.md
    │   ├── 2015-12-08-start-puppet-master.md
    │   ├── 2015-12-10-create-mysql-managed-stack-api.md
    │   ├── 2015-12-10-create-mysql-managed-stack.md
    │   ├── 2016-01-20-create-sqlserver-instance.md
    │   ├── 2016-02-24-how-to-log-your-linux.md
    │   ├── 2016-02-25-android-nxlog.md
    │   ├── 2016-02-25-apache-logs.md
    │   ├── 2016-02-25-filebeat-logs.md
    │   ├── 2016-02-25-windows-nxlog.md
    │   ├── 2016-02-26-bonfire.md
    │   ├── 2016-02-27-djehouty.md
    │   ├── 2016-02-27-logstash-input.md
    │   ├── 2016-02-27-tokens-paas-logs.md
    │   ├── 2016-02-28-field-naming-conventions.md
    │   ├── 2016-02-28-using-grafana-with-laas.md
    │   ├── 2016-02-28-using-timelion-with-laas.md
    │   ├── 2016-02-29-using-kibana-with-laas.md
    │   ├── 2016-03-08-quick-start.md
    │   ├── 2016-04-20-introduction-to-docker-with-mesos-marathon.md
    │   ├── 2016-04-21-quick-start-with-marathon.md
    │   ├── 2016-04-22-marathon-load-balancer.md
    │   ├── 2016-04-23-marathon-health-checks.md
    │   ├── 2016-04-24-marathon-container-logs.md
    │   ├── 2016-04-25-marathon-container-metrics.md
    │   ├── 2016-05-03-how-to-use-deskaas-lab.md
    │   ├── 2016-06-15-getting-started-with-queue-as-a-service.md
    │   ├── 2016-06-17-marathon-api-worker-architecture.markdown
    │   ├── 2016-06-21-deploying-wordpress-on-marathon.md
    │   ├── 2016-06-22-getting-started-with-shinken-as-a-service.md
    │   ├── 2016-06-23-linux-and-skylake.md
    │   ├── 2016-07-04-local-stateful.md
    │   ├── 2016-07-11-service-discovery-with-mesos-dns.md
    │   ├── 2016-07-25-kafka-topics-management.md
    │   ├── 2016-08-17-dbaas-queue-https.md
    │   ├── 2016-10-24-kafka-sasl-ssl.md
    │   ├── 2016-11-07-using-a-private-registry.md
    │   ├── 2017-01-04-getting-started-with-your-private-docker-registry.md
    │   └── 2017-01-31-kafka-metrics-grafana.md
    └── index.html
├── feed.xml
├── images
    ├── 2014-07-28-deploy-load-balanced-wordpress
    │   ├── nfs-word-relation.png
    │   ├── structure.png
    │   ├── word-mysql-rel.png
    │   └── wordpress.png
    ├── 2014-09-09-create-local-network
    │   ├── net_list.png
    │   ├── network_name.png
    │   ├── schema.png
    │   ├── subnet.png
    │   └── subnet_details.png
    ├── 2014-09-25-how-to-install-openvpn-access-server-on-ubuntu-14.04
    │   ├── openvpn1.jpg
    │   ├── openvpn2.jpg
    │   ├── openvpn3.jpg
    │   └── openvpn4.png
    ├── 2014-10-01-create-ssh-keys
    │   ├── putty.png
    │   └── puttygen.png
    ├── 2014-10-06-power8
    │   └── htop.png
    ├── 2014-11-07-private-network-nat
    │   ├── layout.png
    │   ├── network-step1.png
    │   ├── network-step2.png
    │   ├── network-step3.png
    │   └── network-step4.png
    ├── 2014-11-17-send-reliable-emails-from-your-runabove-instance-with-mailjet
    │   └── mailjet.png
    ├── 2014-12-05-how-to-deploy-a-shipyard-cluster-on-runabove
    │   └── shipyard-login.png
    ├── 2014-12-12-docker-in-5-minutes-on-runabove-with-docker-machine
    │   └── docker-logo.png
    ├── 2014-12-29-security-groups
    │   └── add-rule.png
    ├── 2015-01-14-running-wordpress-on-sailabove
    │   └── containers.png
    ├── 2015-01-29-attach-volume
    │   ├── attach.png
    │   ├── create.png
    │   ├── edit-attachments.png
    │   ├── windows-disk-management.png
    │   ├── windows-drives.png
    │   ├── windows-new.png
    │   └── windows-online.png
    ├── 2015-03-12-jekyll-and-swift-object-storage
    │   └── runabove-openstack-rc.png
    ├── 2015-08-10-how-to-manage-iot-applications-using-runabove-manager
    │   ├── application-creation-page.png
    │   ├── application-page.png
    │   ├── empty-application-page.png
    │   ├── token-creation-page.png
    │   ├── token-list.png
    │   └── token-page.png
    ├── 2015-10-13-how-to-use-arm-lab
    │   ├── step1.png
    │   ├── step2.png
    │   ├── step3.png
    │   ├── step4.png
    │   ├── step5.png
    │   ├── step6.png
    │   ├── step7.png
    │   ├── step8.png
    │   └── step9.png
    ├── 2015-10-13-how-to-use-vps-hdd-lab
    │   ├── step1.png
    │   ├── step2.png
    │   ├── step3.png
    │   └── step4.png
    ├── 2015-10-16-how-to-serial-console-arm-instance
    │   ├── goto_dashboard.png
    │   ├── no_console_log.png
    │   ├── no_vnc.png
    │   ├── openstack_creds.png
    │   ├── serial_console.png
    │   └── source_creds.png
    ├── 2015-11-23-use-sailabove-webhook
    │   └── container-states.jpg
    ├── 2015-11-24-how-to-start-simple-puppet-master
    │   └── puppetboard.png
    ├── 2015-11-28-migrate-from-runabove-to-public-cloud
    │   ├── horizon_security_panel.jpg
    │   └── runabove_menu.jpg
    ├── 2015-12-08-start-puppet-master
    │   ├── certificate.png
    │   ├── create-master.png
    │   └── deploykey.png
    ├── 2015-12-10-create-mysql-managed-stack
    │   ├── activate.png
    │   ├── cluster_status.png
    │   ├── delete_stack1.png
    │   ├── delete_stack2.png
    │   ├── menu_managed.png
    │   ├── new_stack.png
    │   ├── signup.png
    │   ├── stack_details.png
    │   ├── start.png
    │   └── status_active.png
    ├── 2016-01-20-create-sqlserver-instance
    │   ├── AddDatabase1.png
    │   ├── AddDatabase2.png
    │   ├── ExplorerSql.png
    │   ├── NewSqlServer.png
    │   ├── NewSqlServer2.png
    │   ├── NewSqlServer3.png
    │   ├── connection.png
    │   ├── databaseActions.png
    │   ├── signup.png
    │   ├── start.png
    │   └── wapPortal.png
    ├── 2016-02-24-how-to-log-your-linux
    │   └── search.png
    ├── 2016-02-25-android-nxlog
    │   ├── graylog.png
    │   └── screen-pid.png
    ├── 2016-02-25-apache-logs
    │   ├── apache-logs.png
    │   └── cheatsheet.png
    ├── 2016-02-25-filebeat-logs
    │   ├── beats_graylog.png
    │   └── filter_graylog.png
    ├── 2016-02-25-windows-nxlog
    │   ├── graylog.png
    │   └── panel_config.png
    ├── 2016-02-27-logstash-input
    │   ├── config_logstash_1.png
    │   ├── filter_section.png
    │   ├── input_section.png
    │   ├── input_start.png
    │   ├── local_logstash_graylog.png
    │   ├── logstash_created.png
    │   ├── logstash_ssl.png
    │   ├── network-input.png
    │   ├── stream_sub.png
    │   └── test_success.png
    ├── 2016-02-27-tokens-paas-logs
    │   ├── postman_1.png
    │   └── rest_easy.png
    ├── 2016-02-28-field-naming-conventions
    │   ├── bytes.png
    │   ├── reserved_keywords.png
    │   └── suffixes.png
    ├── 2016-02-28-using-grafana-with-laas
    │   ├── alias.png
    │   ├── datasource.png
    │   └── grafana.png
    ├── 2016-02-28-using-timelion-with-laas.md
    │   ├── dash.png
    │   ├── timelion-2.png
    │   └── timelion.png
    ├── 2016-02-29-using-kibana-with-laas
    │   ├── alias.png
    │   ├── indice.png
    │   └── kibana.png
    ├── 2016-03-08-quick-start
    │   ├── EnableKibana.png
    │   ├── button.png
    │   ├── critical-dashboard-2.png
    │   ├── critical-dashboard.png
    │   ├── editDashboard.png
    │   ├── editRole.png
    │   ├── editStream.png
    │   ├── graylog-stream.png
    │   ├── inputs-ports.png
    │   ├── kibanaCreated.png
    │   ├── login.png
    │   ├── manager.png
    │   ├── manager_start.png
    │   ├── newAlert.png
    │   ├── newAlias.png
    │   ├── newDashboard.png
    │   ├── newDashboard_2.png
    │   ├── newRole.png
    │   ├── newRole_2.png
    │   ├── newStream.png
    │   ├── newStream_2.png
    │   ├── quick-values.png
    │   ├── roleAcl.png
    │   ├── roleMembers.png
    │   └── start.png
    ├── 2016-04-20-marathon-health-checks
    │   └── health_check.png
    ├── 2016-04-20-quick-start-with-marathon
    │   ├── create_container_1.png
    │   ├── create_container_2.png
    │   ├── create_container_3.png
    │   ├── create_container_4.png
    │   └── marathon.png
    ├── 2016-04-21-marathon-load-balancer
    │   ├── architecture.png
    │   └── haproxy.png
    ├── 2016-04-21-marathon-logs
    │   ├── about.png
    │   ├── labels.png
    │   └── token.png
    ├── 2016-04-21-marathon-metrics
    │   ├── metrics.png
    │   └── metrics_cpu.png
    ├── 2016-05-03-how-to-use-deskaas-lab
    │   ├── offers.png
    │   ├── orderfrommanager.png
    │   ├── soft_authentication.png
    │   ├── soft_list-desktops.png
    │   ├── soft_lists-servers.png
    │   ├── soft_logged-in.png
    │   ├── soft_new-server.png
    │   ├── web_client_desktop.png
    │   ├── web_client_launchitems.png
    │   ├── web_client_login.png
    │   ├── web_client_menu.png
    │   └── web_client_welcome.png
    ├── 2016-06-15-getting-started-with-queue-as-a-service
    │   ├── default_users_credentials.png
    │   ├── queue_description.png
    │   ├── queue_info.png
    │   ├── queue_not_configured_app.png
    │   ├── queue_not_configured_app_menu.png
    │   └── queue_sunrise.png
    ├── 2016-06-17-marathon-api-worker-queue
    │   ├── api.png
    │   ├── api2.png
    │   ├── design.png
    │   ├── redis.png
    │   ├── redis2.png
    │   ├── redis3.png
    │   └── worker.png
    ├── 2016-06-21-deploying-wordpress-on-marathon
    │   ├── phpmyadmin-welcome.png
    │   ├── phpmyadmin.png
    │   ├── phpmyadmin2.png
    │   ├── whitelist.png
    │   ├── wordpress-welcome.png
    │   ├── wordpress.png
    │   └── wordpress2.png
    ├── 2016-06-23-linux-and-skylake
    │   ├── distrib_kernel.png
    │   ├── rescue1.png
    │   └── rescue2.png
    ├── 2016-07-25-kafka-topics-management
    │   └── sunrise-topics.png
    ├── 2016-08-17-dbaas-queue-https
    │   └── sunrise-info.png
    ├── 2016-10-24-kafka-sasl-ssl
    │   ├── sunrise-roles.png
    │   └── sunrise-users.png
    ├── 2016-11-07-using-a-private-registry
    │   └── private-registry.png
    ├── 2017-01-04-how-to-start-with-your-private-docker-registry
    │   ├── accounts_listing.png
    │   ├── images_listing.png
    │   ├── namespace_creation.png
    │   ├── namespace_details.png
    │   ├── user_creation.png
    │   ├── user_listing.png
    │   └── user_permissions_add.png
    ├── 2017-01-31-kafka-metrics-grafana
    │   ├── Screenshot from 2017-01-29 21-41-29.png
    │   ├── applications_list.png
    │   ├── credentials.png
    │   ├── data_source.png
    │   ├── datasource_configuration.png
    │   ├── graph_with_tag.png
    │   ├── graph_without_tag.png
    │   ├── new_graph.png
    │   ├── new_organization.png
    │   └── select_datasource.png
    ├── author-github.png
    ├── community
    │   ├── arrowLink.png
    │   ├── gear.png
    │   └── user.png
    ├── favicon.ico
    ├── github.png
    ├── icon-gitHub-footer.png
    ├── icon-twitter-footer.png
    ├── logo-top.png
    └── twitter.png
├── index.html
├── js
    ├── embed.min.js
    └── responsive-nav.js
└── styles
    ├── community.css
    ├── fonts-lato.css
    ├── fonts
        └── lato
        │   ├── lato-light-webfont.woff
        │   └── lato-regular-webfont.woff
    ├── highlight.css
    ├── images
        └── twitter.png
    ├── knowledge-base.css
    ├── main.css
    ├── responsive-nav.css
    ├── responsive.css
    └── styles-nav.css


/.gitignore:
--------------------------------------------------------------------------------
1 | _site


--------------------------------------------------------------------------------
/CONTRIBUTING.md:
--------------------------------------------------------------------------------
1 | ---
2 | layout: page
3 | title: Contributing
4 | lang: en
5 | ---
6 | 
7 | The knowledge base is accessible for everyone. Everyone can contribute by forking the Github repository [github.com/runabove/knowledge-base](https://github.com/runabove/knowledge-base)
8 | 


--------------------------------------------------------------------------------
/Dockerfile:
--------------------------------------------------------------------------------
 1 | FROM ruby:1.9-onbuild
 2 | 
 3 | MAINTAINER RunAbove <contact@runabove.com>
 4 | 
 5 | EXPOSE 4000
 6 | 
 7 | RUN apt-get update && apt-get -yy install nodejs
 8 | RUN jekyll build
 9 | 
10 | CMD jekyll serve --host 0.0.0.0 --port 4000
11 | 


--------------------------------------------------------------------------------
/Gemfile:
--------------------------------------------------------------------------------
1 | source 'https://rubygems.org'
2 | gem 'jekyll', '2.3.0'
3 | 
4 | 


--------------------------------------------------------------------------------
/Gemfile.lock:
--------------------------------------------------------------------------------
 1 | GEM
 2 |   remote: https://rubygems.org/
 3 |   specs:
 4 |     addressable (2.4.0)
 5 |     blankslate (2.1.2.4)
 6 |     classifier-reborn (2.0.4)
 7 |       fast-stemmer (~> 1.0)
 8 |     coffee-script (2.4.1)
 9 |       coffee-script-source
10 |       execjs
11 |     coffee-script-source (1.10.0)
12 |     colorator (0.1)
13 |     execjs (2.7.0)
14 |     faraday (0.9.2)
15 |       multipart-post (>= 1.2, < 3)
16 |     fast-stemmer (1.0.2)
17 |     ffi (1.9.10)
18 |     jekyll (2.3.0)
19 |       classifier-reborn (~> 2.0)
20 |       colorator (~> 0.1)
21 |       jekyll-coffeescript (~> 1.0)
22 |       jekyll-gist (~> 1.0)
23 |       jekyll-paginate (~> 1.0)
24 |       jekyll-sass-converter (~> 1.0)
25 |       jekyll-watch (~> 1.1)
26 |       kramdown (~> 1.3)
27 |       liquid (~> 2.6.1)
28 |       mercenary (~> 0.3.3)
29 |       pygments.rb (~> 0.6.0)
30 |       redcarpet (~> 3.1)
31 |       safe_yaml (~> 1.0)
32 |       toml (~> 0.1.0)
33 |     jekyll-coffeescript (1.0.1)
34 |       coffee-script (~> 2.2)
35 |     jekyll-gist (1.4.0)
36 |       octokit (~> 4.2)
37 |     jekyll-paginate (1.1.0)
38 |     jekyll-sass-converter (1.4.0)
39 |       sass (~> 3.4)
40 |     jekyll-watch (1.4.0)
41 |       listen (~> 3.0, < 3.1)
42 |     kramdown (1.11.1)
43 |     liquid (2.6.3)
44 |     listen (3.0.8)
45 |       rb-fsevent (~> 0.9, >= 0.9.4)
46 |       rb-inotify (~> 0.9, >= 0.9.7)
47 |     mercenary (0.3.6)
48 |     multipart-post (2.0.0)
49 |     octokit (4.3.0)
50 |       sawyer (~> 0.7.0, >= 0.5.3)
51 |     parslet (1.5.0)
52 |       blankslate (~> 2.0)
53 |     posix-spawn (0.3.11)
54 |     pygments.rb (0.6.3)
55 |       posix-spawn (~> 0.3.6)
56 |       yajl-ruby (~> 1.2.0)
57 |     rb-fsevent (0.9.7)
58 |     rb-inotify (0.9.7)
59 |       ffi (>= 0.5.0)
60 |     redcarpet (3.3.4)
61 |     safe_yaml (1.0.4)
62 |     sass (3.4.22)
63 |     sawyer (0.7.0)
64 |       addressable (>= 2.3.5, < 2.5)
65 |       faraday (~> 0.8, < 0.10)
66 |     toml (0.1.2)
67 |       parslet (~> 1.5.0)
68 |     yajl-ruby (1.2.1)
69 | 
70 | PLATFORMS
71 |   ruby
72 | 
73 | DEPENDENCIES
74 |   jekyll (= 2.3.0)
75 | 
76 | BUNDLED WITH
77 |    1.12.5
78 | 


--------------------------------------------------------------------------------
/Makefile:
--------------------------------------------------------------------------------
 1 | 
 2 | .PHONY: help
 3 | 
 4 | # self-documented makefile
 5 | help:
 6 | 	@grep -E '^[a-zA-Z_-]+:.*?## .*$$' $(MAKEFILE_LIST) | sort | awk 'BEGIN {FS = ":.*?## "}; {printf "\033[36m%-30s\033[0m %s\n", $$1, $$2}'
 7 | 
 8 | 
 9 | build: ## build a docker image named knowledge-base, serving a local version of the knowledge-base on port 4000
10 | 	docker build -t knowledge-base .
11 | 
12 | run: build  ## Run a local version of the knowledge-base and serve it on localhost:4000/kb/
13 | 	docker run -ti --rm -p 4000:4000 knowledge-base 
14 | 


--------------------------------------------------------------------------------
/README.md:
--------------------------------------------------------------------------------
  1 | This repository contains tutorials of [RunAbove Knowledge
  2 | base](https://community.runabove.com/kb).
  3 | 
  4 | # How to write a how-to guide?
  5 | 
  6 | Simply fork the runabove/knowledge-base project on our GitHub page. Create a
  7 | new page under [/en/_posts](en/_posts) and using markdown to write your how-to
  8 | guide. Please refer to the metadata in existing guides so that you add adequate
  9 | metadata at the beginning of your guide. Feel free to create a folder for your
 10 | images in [/images](images).
 11 | 
 12 | Please note that we may not accept your how-to guide if it doesn’t fit our
 13 | review criteria. Here is a list of some of the main points we’ll take into
 14 | account:
 15 | 
 16 |  * Your guide is written in English.
 17 |  * Any prerequisites for carrying out the steps in the guide are listed in your
 18 |  guide’s intro.
 19 |  * Any usage you encourage is completely legal and respects good practices and
 20 |  security standards.
 21 |  * Content is your own and doesn’t include any copyrighted content (including
 22 |  images). Your proposal should be exclusively published on our website.
 23 | 
 24 | Please also keep in mind that we’re mainly interested in how-to guides on
 25 | open-source tools and integration with popular tier technologies.
 26 | 
 27 | # Quick start your new tutorial:
 28 | 
 29 | ## Create your tutorial
 30 | 
 31 | Fork runabove/knowledge-base repository and get the content on your machine.
 32 | 
 33 | ```
 34 | git clone https://github.com/your_github_username/knowledge-base.git
 35 | ```
 36 | 
 37 | Add a file inside __posts__ directory with this template:
 38 | 
 39 | ```markdown
 40 | ---
 41 | layout: post
 42 | title:  "My first tutorial"
 43 | categories: Instances
 44 | author: your_github_username
 45 | lang: en
 46 | ---
 47 | 
 48 | # Here you can add your tutorial
 49 | 
 50 | With markdown syntax.
 51 | ```
 52 | 
 53 | ## Test your tutorial
 54 | 
 55 | ### With Docker (recommended)
 56 | 
 57 | The easiest way to test how your guide renders on RunAbove website is to build
 58 | and run the Docker container.
 59 | 
 60 | ```bash
 61 | docker build --tag runabove-kb .
 62 | docker run --rm -ti -p 4000:4000 runabove-kb
 63 | ```
 64 | 
 65 | You can now point your browser to http://localhost:4000/kb/ and see how it
 66 | looks.
 67 | 
 68 | ### Installing Jekyll
 69 | 
 70 | To deploy tutorials on runabove, we use a ruby tool called
 71 | [Jekyll](http://jekyllrb.com/). You can find more informations about Jekyll
 72 | installation inside the [official
 73 | documentation](http://jekyllrb.com/docs/installation/). Get it up and running:
 74 | 
 75 | ```bash
 76 | curl -sSL https://get.rvm.io | bash -s stable --ruby=1.9.3 --autolibs=fail
 77 | curl https://raw.githubusercontent.com/creationix/nvm/v0.25.1/install.sh | bash
 78 | nvm install 0.10
 79 | nvm use 0.10
 80 | source ~/.bashrc
 81 | gem install bundler
 82 | bundle
 83 | ```
 84 | 
 85 | Inside root directory of the project, you can run this command to generate the
 86 | website and see your guide:
 87 | 
 88 | ```bash
 89 | bundle exec jekyll build
 90 | ```
 91 | 
 92 | You website is now inside `_site` directory.
 93 | 
 94 | You can also run this command to have jekyll serve your static pages :
 95 | 
 96 | ```bash
 97 | bundle exec jekyll serve
 98 | ```
 99 | 
100 | When you’re done, open a pull request for your fork. We'll review it as soon
101 | as possible!
102 | 
103 | # Got a great idea? Fork us now!
104 | 
105 | 


--------------------------------------------------------------------------------
/_config.yml:
--------------------------------------------------------------------------------
 1 | # Website  settings
 2 | title: RunAbove knowledge base
 3 | email: developers@runabove.com
 4 | description: "Public knowledge base for RunAbove users."
 5 | baseurl: "/kb"
 6 | url: "https://community.runabove.com"
 7 | twitter_username: runabove
 8 | github_username: runabove
 9 | 
10 | # Build settings
11 | markdown: redcarpet
12 | highlighter: pygments
13 | permalink: none
14 | 
15 | # Pagination
16 | paginate: 7
17 | paginate_path: "/page:num"
18 | paginate_categories: true
19 | 
20 | # Categories plugin settings
21 | category_dir: category
22 | category_title_prefix: ""
23 | 
24 | # Languages
25 | languages: [en]
26 | 
27 | # Translations
28 | t:
29 |   home:
30 |     en:
31 |       categories: "Categories"
32 |       latest_articles: "Latest tutorials"
33 |   nav:
34 |     en:
35 |       contributing: "Contributing"
36 |       read_in: "Read in English"
37 |       subscribe: "Subscribe via"
38 |   category:
39 |     en:
40 |       filed_under: "Filed under"
41 | 


--------------------------------------------------------------------------------
/_includes/custom/category_feed.xml:
--------------------------------------------------------------------------------
 1 | ---
 2 | layout: nil
 3 | ---
 4 | <?xml version="1.0" encoding="utf-8"?>
 5 | <feed xmlns="http://www.w3.org/2005/Atom">
 6 | 
 7 |   <title><![CDATA[{{ page.title }} | {{ site.title }}]]></title>
 8 |   <link href="{{ site.url }}/{{ page.feed_url }}" rel="self"/>
 9 |   <link href="{{ site.url }}/"/>
10 |   <updated>{{ site.time | date_to_xmlschema }}</updated>
11 |   <id>{{ site.url }}/</id>
12 |   <author>
13 |     <name><![CDATA[{{ site.author | strip_html }}]]></name>
14 |     {% if site.email %}<email><![CDATA[{{ site.email }}]]></email>{% endif %}
15 |   </author>
16 |   <generator uri="https://github.com/recurser/jekyll-plugins">Recurser</generator>
17 | 
18 |   {% for post in site.categories[page.category] limit: 10 %}
19 |   <entry>
20 |     <title type="html"><![CDATA[{{ post.title | cdata_escape }}]]></title>
21 |     <link href="{{ site.url }}{{ post.url }}"/>
22 |     <updated>{{ post.date | date_to_xmlschema }}</updated>
23 |     <id>{{ site.url }}{{ post.id }}</id>
24 |     <content type="html"><![CDATA[{{ post.content | expand_urls: site.url | markdownify | cdata_escape }}]]></content>
25 |   </entry>
26 |   {% endfor %}
27 | </feed>
28 | 


--------------------------------------------------------------------------------
/_includes/custom/category_json.json:
--------------------------------------------------------------------------------
 1 | ---
 2 | layout: nil
 3 | ---
 4 | [
 5 |   {% for post in site.categories[page.category] limit: 10 %}
 6 |     {
 7 |         "title": "{{ post.title }}",
 8 |         "url": "{{site.url}}{{ site.baseurl }}{{ post.url }}"
 9 |     }{% unless forloop.last %},{% endunless %}
10 |   {% endfor %}
11 | ]
12 | 


--------------------------------------------------------------------------------
/_includes/footer.html:
--------------------------------------------------------------------------------
 1 | 
 2 | <div class="full Fleft SecondFooter">
 3 | 	<div class="wrapper">
 4 | 		<ul class="Fleft" style="width: 33%">
 5 | 			<li class="">
 6 | 				<a href="https://cloud.runabove.com/#/support" target="">Support</a>
 7 | 			</li>
 8 | 			<li class="">
 9 | 				<a href="{{ site.baseurl }}/attachments/Special_Conditions_Betatest_OVH-COM.pdf" target="_blank">Terms of Service</a>
10 | 			</li>
11 | 		</ul>
12 | 
13 | 		<ul class="Fleft" style="width: 33%">
14 | 			<li class="grey center" style="display:block;line-height:60px;">© 2017 - runabove. all rights reserved.</li>
15 | 		</ul>
16 | 
17 | 		<ul class="Fright" style="width: 33%">
18 | 			<li class="SocialIcn">
19 | 				<a href="https://twitter.com/runabove" target="_blank">
20 | 					<img src="{{ site.baseurl }}/images/icon-twitter-footer.png">
21 | 				</a>
22 | 			</li>
23 | 			<li class="SocialIcn">
24 | 				<a href="https://github.com/runabove" target="_blank">
25 | 					<img src="{{ site.baseurl }}/images/icon-gitHub-footer.png">
26 | 				</a>
27 | 			</li>
28 | 		</ul>
29 | 	</div>
30 | 
31 |         <script type="text/javascript">
32 |         <!-- Piwik -->
33 |             var _paq = _paq || [];
34 |             _paq.push(["setDocumentTitle", document.domain + "/" + document.title]);
35 |             _paq.push(["setCookieDomain", "*.runabove.com"]);
36 |             _paq.push(["trackPageView"]);
37 |             _paq.push(["enableLinkTracking"]);
38 | 
39 |             (function() {
40 |                 var u=(("https:" == document.location.protocol) ? "https" : "http") + "://webanalytics2.ovh.net/";
41 |                 _paq.push(["setTrackerUrl", u+"piwik.php"]);
42 |                 _paq.push(["setSiteId", "30"]);
43 |                 var d=document, g=d.createElement("script"), s=d.getElementsByTagName("script")[0]; g.type="text/javascript";
44 |                 g.defer=true; g.async=true; g.src=u+"piwik.js"; s.parentNode.insertBefore(g,s);
45 |             })();
46 |         </script>
47 |         <script language="javascript" type="text/javascript" src="https://webanalytics2.ovh.net/piwik.js"></script>
48 |         <!-- End Piwik Code -->
49 | 
50 |         </script>
51 |         <noscript><p><img src="https://webanalytics2.ovh.net/piwik.php?idsite=30&amp;rec=1" style="border:0" alt=""></p></noscript>
52 | </div>
53 | 


--------------------------------------------------------------------------------
/_includes/head.html:
--------------------------------------------------------------------------------
 1 | <meta charset="utf-8">
 2 | <meta http-equiv="Content-Type" content="text/html; charset=utf-8">
 3 | <title>{% if page.title %}{{ page.title }} - {% endif %}{{ site.title }}</title>
 4 | <meta http-equiv="X-UA-Compatible" content="IE=edge,chrome=1">
 5 | <link rel="shortcut icon" href="{{ site.baseurl }}/images/favicon.ico">
 6 | <meta name="viewport" content="width=device-width,initial-scale=1">
 7 | <link href="{{ "/styles/main.css" | prepend: site.baseurl }}" rel="stylesheet" type="text/css">
 8 | <link href="{{ "/styles/fonts-lato.css" | prepend: site.baseurl }}" rel="stylesheet" type="text/css">
 9 | <link href="{{ "/styles/responsive-nav.css" | prepend: site.baseurl }}" rel="stylesheet" type="text/css">
10 | <link href="{{ "/styles/responsive.css" | prepend: site.baseurl }}" rel="stylesheet" type="text/css">
11 | <link href="{{ "/styles/community.css" | prepend: site.baseurl }}" rel="stylesheet" type="text/css">
12 | <link href="{{ "/styles/styles-nav.css" | prepend: site.baseurl }}" rel="stylesheet" type="text/css">
13 | <link href="{{ "/styles/highlight.css" | prepend: site.baseurl }}" rel="stylesheet" type="text/css">
14 | <link href="{{ "/styles/knowledge-base.css" | prepend: site.baseurl }}" rel="stylesheet" type="text/css">
15 | {% if page.description %}<meta name="description" content="{{ page.description }}">{% endif %}
16 | 


--------------------------------------------------------------------------------
/_layouts/category_index.html:
--------------------------------------------------------------------------------
 1 | ---
 2 | layout: default
 3 | ---
 4 | 
 5 | <div class="home">
 6 | 
 7 |   <p class="arian">
 8 |     <span itemscope itemtype="http://data-vocabulary.org/Breadcrumb">
 9 |       <a  itemprop="url"
10 |           href="https://community.runabove.com">
11 |         <span itemprop="title">Community</span>
12 |       </a>
13 |     </span> &gt;
14 |     <span itemscope itemtype="http://data-vocabulary.org/Breadcrumb">
15 |       <a  href="{{ site.baseurl }}"
16 |           href="https://community.runabove.com">
17 |         <span itemprop="title">Knowledge base</span>
18 |       </a>
19 |     </span>&gt;
20 |   </p>
21 | 
22 |   <h2>{{ page.title }}</h2>
23 | 
24 |   <div class="tutorials" id="tutorials">
25 |     <div>
26 | 			{% for post in paginator.posts %}
27 |         <div class="tutorial">
28 |           <h4><a href="{{ post.url | prepend: site.baseurl }}">{{ post.title }}</a></h4>
29 |           <p class="author">
30 |             {% if post.author %}
31 |               by <a href="https://github.com/{{ post.author }}">
32 |                 {{ post.author }}
33 |               </a>
34 |             {% endif %}
35 |             <span class="date">
36 |               {{ post.date | date: "%b %-d, %Y" }}
37 |             </span>
38 |           </p>
39 |           <p class="content">
40 |             {{ post.content | markdownify | strip_html | truncatewords: 50 }}
41 |           </p>
42 |           <a href="{{ post.url | prepend: site.baseurl }}" class="link">
43 |             read the tutorial
44 |           </a>
45 |           <br>
46 |         </div>
47 |       {% endfor %}
48 |     </div>
49 |   </div>
50 | 
51 |   {% if paginator.total_pages > 1 %}
52 |     <div class="pagination">
53 |   {% if paginator.previous_page %}
54 |         <a href="{{ paginator.previous_page_path | prepend: page.category_dir | replace: '//', '/' }}">&laquo; Prev</a>
55 |   {% else %}
56 |     <span>&laquo; Prev</span>
57 |   {% endif %}
58 | 
59 |   {% for p in (1..paginator.total_pages) %}
60 |     {% if p == paginator.page %}
61 |       <em>{{ p }}</em>
62 |     {% elsif p == 1 %}
63 |       <a href="{{ '/index.html' | prepend: page.category_dir | replace: '//', '/' }}">{{ p }}</a>
64 |     {% else %}
65 |       <a href="{{ site.paginate_path | prepend: page.category_dir | replace: '//', '/' | replace: ':num', p }}">{{ p }}</a>
66 |     {% endif %}
67 |   {% endfor %}
68 | 
69 |   {% if paginator.next_page %}
70 |         <a href="{{ paginator.next_page_path | prepend: page.category_dir | replace: '//', '/' }}">Next &raquo;</a>
71 |     {% else %}
72 |         <span>Next &raquo;</span>
73 |   {% endif %}
74 |     </div>
75 |   {% endif %}
76 | 
77 | </div>
78 | 


--------------------------------------------------------------------------------
/_layouts/default.html:
--------------------------------------------------------------------------------
 1 | <!DOCTYPE html>
 2 | <html lang="{{ page.lang }}">
 3 | 
 4 | 	<head>
 5 | 		{% include head.html %}
 6 | 	</head>
 7 | 
 8 | 	<body>
 9 | 
10 | 		{% include header.html %}
11 | 
12 | 		<div class="full fl body">
13 | 			<div class="wrapper"><br><br>
14 | 				<div class="w75 mAuto community">
15 | 					{{ content }}
16 | 				</div>
17 | 			</div>
18 | 		</div>
19 | 
20 | 		{% include footer.html %}
21 | 
22 | 	</body>
23 | </html>
24 | 


--------------------------------------------------------------------------------
/_layouts/home.html:
--------------------------------------------------------------------------------
 1 | ---
 2 | layout: default
 3 | ---
 4 | 
 5 | <div class="home">
 6 | 
 7 |   <p class="arian">
 8 |     <span itemscope itemtype="http://data-vocabulary.org/Breadcrumb">
 9 |       <a  itemprop="url"
10 |           href="https://community.runabove.com">
11 |         <span itemprop="title">Community</span>
12 |       </a>
13 |     </span> &gt;
14 |     <span itemscope itemtype="http://data-vocabulary.org/Breadcrumb">
15 |       <a  href="{{ site.baseurl }}"
16 |           itemprop="url">
17 |         <span itemprop="title">Knowledge base</span>
18 |       </a>
19 |     </span>&gt;
20 |   </p>
21 | 
22 |   <h1>{{ site.t.home[page.lang].latest_articles }}</h1>
23 | 
24 |   <div class="tutorials" id="tutorials">
25 |     <div>
26 |       {% for post in paginator.posts %}
27 |         <div class="tutorial">
28 |           <h4><a href="{{ post.url | prepend: site.baseurl }}">{{ post.title }}</a></h4>
29 |           <p class="author">
30 |             {% if post.author %}
31 |               by <a href="https://github.com/{{ post.author }}">
32 |                 {{ post.author }}
33 |               </a>
34 |             {% endif %}
35 |             <span class="date">
36 |               {{ post.date | date: "%b %-d, %Y" }}
37 |             </span>
38 |           </p>
39 |           <p class="content">
40 |             {{ post.content | markdownify | strip_html | truncatewords: 50 }}
41 |           </p>
42 |           <a href="{{ post.url | prepend: site.baseurl }}" class="link">
43 |             read the tutorial
44 |           </a>
45 |           <br>
46 |         </div>
47 |       {% endfor %}
48 |     </div>
49 |   </div>
50 | 
51 |   {% if paginator.total_pages > 1 %}
52 |     <div class="pagination">
53 | 	{% if paginator.previous_page %}
54 |     	  <a href="{{ paginator.previous_page_path | prepend: site.baseurl | replace: '//', '/' }}">&laquo; Prev</a>
55 | 	{% else %}
56 | 	  <span>&laquo; Prev</span>
57 | 	{% endif %}
58 | 
59 | 	{% for page in (1..paginator.total_pages) %}
60 | 	  {% if page == paginator.page %}
61 | 	    <em>{{ page }}</em>
62 | 	  {% elsif page == 1 %}
63 | 	    <a href="{{ '/index.html' | prepend: site.baseurl | replace: '//', '/' }}">{{ page }}</a>
64 | 	  {% else %}
65 | 	    <a href="{{ site.paginate_path | prepend: site.baseurl | replace: '//', '/' | replace: ':num', page }}">{{ page }}</a>
66 | 	  {% endif %}
67 | 	{% endfor %}
68 | 
69 | 	{% if paginator.next_page %}
70 |     	  <a href="{{ paginator.next_page_path | prepend: site.baseurl | replace: '//', '/' }}">Next &raquo;</a>
71 |   	{% else %}
72 |     	  <span>Next &raquo;</span>
73 | 	{% endif %}
74 |     </div>
75 |   {% endif %}  
76 | 
77 | </div>
78 | 


--------------------------------------------------------------------------------
/_layouts/page.html:
--------------------------------------------------------------------------------
 1 | ---
 2 | layout: default
 3 | ---
 4 | <div class="post">
 5 | 
 6 |   <h1>{{ page.title }}</h1>
 7 | 
 8 |   {{ content }}
 9 | 
10 | </div>
11 | 


--------------------------------------------------------------------------------
/_layouts/post.html:
--------------------------------------------------------------------------------
 1 | ---
 2 | layout: root
 3 | ---
 4 |   <p class="arian">
 5 |     <span itemscope itemtype="http://data-vocabulary.org/Breadcrumb">
 6 |       <a  itemprop="url"
 7 |           href="https://community.runabove.com">
 8 |         <span itemprop="title">Community</span>
 9 |       </a>
10 |     </span> &gt;
11 |     <span itemscope itemtype="http://data-vocabulary.org/Breadcrumb">
12 |       <a  href="{{ site.baseurl }}"
13 |           itemprop="url">
14 |         <span itemprop="title">Knowledge base</span>
15 |       </a>
16 |     </span>&gt;
17 |     <span itemscope itemtype="http://data-vocabulary.org/Breadcrumb">
18 |       <a  href="{{ site.baseurl }}/en/{{ page.categories[1] }}"
19 |           itemprop="url">
20 |         <span itemprop="title">{{ page.categories[1] }}</span>
21 |       </a>
22 |     </span> &gt;
23 |   </p>
24 | 
25 |     <h1>{{ page.title }}</h1>
26 |     <p class="meta">{{ page.date | date: "%b %-d, %Y" }}
27 |     {% if page.meta %} • {{ page.meta }}{% endif %}
28 |     {% if page.author %} •
29 |       <img class="github_icon" src="{{ site.baseurl }}/images/author-github.png" alt="Github account" />
30 |       <a href="https://github.com/{{ page.author }}">{{ page.author }}</a>
31 |     {% endif %}</p>
32 |     <p class="meta">
33 |       {% if page.trans %}
34 |         {% for trans in page.trans %}
35 |           {% assign p = trans[1] | prepend: '/_posts/' | prepend: trans[0] %}
36 |           {% for post in site.posts %}
37 |       	    {% if post.path == p %}
38 |             {% assign lang = trans[0] %}
39 |               <a href="{{post.url}}">{{ site.t.nav[lang].read_in }}</a>
40 |             {% endif %}
41 |           {% endfor %}
42 |         {% endfor %}
43 |       {% endif %}
44 |     </p>
45 | 
46 |     <div class="post-content">
47 |     {{ content }}
48 |     </div>
49 | 
50 | 


--------------------------------------------------------------------------------
/_layouts/redirected.html:
--------------------------------------------------------------------------------
 1 | <!DOCTYPE html>
 2 | <html>
 3 | <head>
 4 | <link rel="canonical" href="{{ page.redirect_to }}"/>
 5 | <meta http-equiv="content-type" content="text/html; charset=utf-8" />
 6 | <meta http-equiv="refresh" content="0;url={{ page.redirect_to }}" />
 7 | </head>
 8 | <body>
 9 |     <h1>Redirecting...</h1>
10 |       <a href="{{ page.redirect_to }}">Click here if you are not redirected.<a>
11 |       <script>location='{{ page.redirect_to }}'</script>
12 | </body>
13 | </html>
14 | 


--------------------------------------------------------------------------------
/_layouts/root.html:
--------------------------------------------------------------------------------
 1 | <!DOCTYPE html>
 2 | <html lang="{{ page.lang }}">
 3 | 
 4 | 	<head>
 5 | 		{% include head.html %}
 6 | 		<meta name="description" content="{{ page.content | markdownify | strip_html | truncatewords: 50 }}..." />
 7 | 	</head>
 8 | 
 9 | 	<body>
10 | 
11 | 		{% include header.html %}
12 | 
13 | 		<div class="full fl body">
14 | 			<div class="wrapper"><br><br>
15 | 				<div class="w75 mAuto community">
16 | 					{{ content }}
17 | 				</div>
18 | 			</div>
19 | 		</div>
20 | 
21 | 		{% include footer.html %}
22 | 
23 | 	</body>
24 | </html>
25 | 


--------------------------------------------------------------------------------
/_plugins/octopress_filters.rb:
--------------------------------------------------------------------------------
 1 | # Filters taken from the Octopress project by Brandon Mathis.
 2 | # https://github.com/imathis/octopress/blob/master/plugins/octopress_filters.rb
 3 | module Jekyll
 4 | 
 5 |   module Filters
 6 | 
 7 |     # Escapes CDATA sections in post content
 8 |     def cdata_escape(input)
 9 |       input.gsub(/<!\[CDATA\[/, '&lt;![CDATA[').gsub(/\]\]>/, ']]&gt;')
10 |     end
11 | 
12 |     # Replaces relative urls with full urls
13 |     def expand_urls(input, url='')
14 |       url ||= '/'
15 |       input.gsub /(\s+(href|src)\s*=\s*["|']{1})(\/[^\"'>]*)/ do
16 |         $1+url+$3
17 |       end
18 |     end
19 | 
20 |   end
21 | 
22 | end


--------------------------------------------------------------------------------
/attachments/Special_Conditions_Betatest_OVH-COM.pdf:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/ovhlabs/knowledge-base/b6339a6f5d858fcee972f4c4a451870bf7464d26/attachments/Special_Conditions_Betatest_OVH-COM.pdf


--------------------------------------------------------------------------------
/en/_posts/2014-04-14-how-to-deploy-core-os-on-runabove.markdown:
--------------------------------------------------------------------------------
 1 | ---
 2 | layout: post
 3 | title:  "How to deploy CoreOS on RunAbove?"
 4 | categories: Instances
 5 | author: yadutaf
 6 | lang: en
 7 | ---
 8 | CoreOS is Linux for Massive Server Deployments. It leverages state of the art software like [Docker](https://www.docker.com/) and [systemd](http://fr.wikipedia.org/wiki/Systemd) to become *the* cluster operating system.
 9 | 
10 | It supports painless upgrade, service discovery, overlay networks, Ceph, ... In a word, it's awesome!
11 | 
12 | And deploying it on Runabove is a breeze.
13 | 
14 | # 1. Create a custom VM template
15 | 
16 | Go the [OpenStack Horizon](https://cloud.runabove.com/horizon/), then go to _Images_ panel and then on the _create image_ button to install the new image.
17 | 
18 | ![](https://storage.bhs-1.runabove.io/v1/AUTH_3eca649cc7f44d91b67131374db4afb3/public/coreos_screenshot1.jpg)
19 | 
20 | CoreOS distributes official OpenStack compressed images that we'll need to prepare. For example:
21 | 
22 | ```
23 | wget http://alpha.release.core-os.net/amd64-usr/current/coreos_production_openstack_image.img.bz2
24 | bunzip2 coreos_production_openstack_image.img.bz2
25 | ```
26 | 
27 | You can then upload resulting ``coreos_production_openstack_image.img`` file (around 400MB). Alternatively You'll find an already [inflated images of CoreOS 431 here](https://storage.bhs-1.runabove.io/v1/AUTH_721b7c504d1b476691659bfee21308d8/public/CoreOS-431.img).
28 | 
29 | # 2. Launch an instance from this image
30 | 
31 | Click the _Launch_ button right next to your new image.
32 | 
33 | Pick a cool name for your instance. Say ``agent_007``. Make sure to select a network like ``Ext-Net``. Then move on to the _post-creation_ tab.
34 | 
35 | # 3. Configure your instance
36 | 
37 | ![](https://storage.bhs-1.runabove.io/v1/AUTH_3eca649cc7f44d91b67131374db4afb3/public/coreos_screenshot3.jpg)
38 | 
39 | If you don't have one already, generate a unique token to identify your new CoreOS cluster. This token will allow cluster members to automatically discover their peers.
40 | 
41 | ```
42 | curl https://discovery.etcd.io/new; echo
43 | ```
44 | 
45 | Paste and customize the following [cloud-config](https://coreos.com/docs/cluster-management/setup/cloudinit-cloud-config/) script. Cloud-config is the standard for VM customization and especially well integrated by CoreOS team.
46 | 
47 | ```yaml
48 | #cloud-config
49 | coreos:
50 |   etcd:
51 |     # <token> as generated above
52 |     discovery: https://discovery.etcd.io/<token>
53 |     addr: $private_ipv4:4001
54 |     peer-addr: $private_ipv4:7001
55 |   units:
56 |     - name: etcd.service
57 |       command: start
58 |     - name: fleet.service
59 |       command: start
60 | ```
61 | 
62 | # Launch... And voilà !
63 | 
64 | Don't forget to login with the user `core` instead of `admin` or `root`!
65 | 
66 | ![](https://storage.bhs-1.runabove.io/v1/AUTH_3eca649cc7f44d91b67131374db4afb3/public/coreos_nodes.jpg)
67 | 
68 | You can find more information: https://coreos.com/docs/running-coreos/platforms/openstack/
69 | 


--------------------------------------------------------------------------------
/en/_posts/2014-04-17-how-to-create-a-compute-instance-in-few-seconds.markdown:
--------------------------------------------------------------------------------
 1 | ---
 2 | layout: post
 3 | title:  "How to create instances in few seconds?"
 4 | categories: Instances
 5 | author: VincentCasse
 6 | lang: en
 7 | ---
 8 | 
 9 | In RunAbove, it is possible to create new instances with dedicated hardware in few seconds! But how you can create new instances?
10 | 
11 | # Generate an SSH key
12 | 
13 | The first time you create a instance, you will need to add a new SSH key. This key will be used to administer your server. To create a new SSH key, you can use ssh-keygen. Your public key will be available in _.ssh/id_rsa.pub_
14 | 
15 | ```
16 | ssh-keygen -t rsa -b 4096 -C "firstname.lastname@domain.com"
17 | ```
18 | 
19 | # Open your manager
20 | 
21 | Open RunAbove [Control panel](https://cloud.runabove.com) with your login details.
22 | 
23 | ![](https://lb1049.pcs.ovh.net/v1/AUTH_e17900908d244c4bb80525f0c0d3a227/public/how-to-create-a-compute-instance-in-two-minutes.html/login_runabove.png)
24 | 
25 | # Add a new instance
26 | 
27 | Click on __Add__ in the left-hand menu and choose to add an __Instance__.
28 | 
29 | Fill in the form with your custom configuration:
30 | 
31 |  * Image is the distribution you choose
32 |  * Region is the area where the instance is stored
33 |  * Template is the hardware profile you want
34 | 
35 | If you don't already have registered a SSH key, select __Create an SSH key__ and give it a name, and copy the content of your public key.
36 | 
37 | ![](https://community.runabove.com/public/files/4sSRjnRagduTmpyhCoU7.png)
38 | 
39 | # Your instance is ready!
40 | 
41 | When the status of your instance is __active__, you can access your server with SSH
42 | 
43 | ```
44 | ssh admin@ip.of.your.vm
45 | ```


--------------------------------------------------------------------------------
/en/_posts/2014-04-17-spinning-up-instances-with-saltstack.markdown:
--------------------------------------------------------------------------------
 1 | ---
 2 | layout: post
 3 | title:  "Spinning up instances with saltstack / salt-cloud"
 4 | categories: Instances
 5 | author: Jean Sébastien Bruneau
 6 | lang: en
 7 | ---
 8 | 
 9 | There are quite a few devops tools out there, i like saltstack and thanks to the openstack backend of runabove, you can spin up instances with salt-cloud!
10 | 
11 | You need to have salt, libcloud and salt-cloud installed, i am running these versions.
12 | ```
13 | jsb@dev:/etc/salt$ salt-cloud --versions-report
14 |             Salt: 2014.1.0-4765-gcbe7c7e
15 |             Python: 2.7.3 (default, Feb 27 2014, 19:58:35)
16 |             Jinja2: 2.6[
17 |             M2Crypto: 0.21.1
18 |             msgpack-python: 0.1.10
19 |             msgpack-pure: Not Installed
20 |             pycrypto: 2.4.1
21 |             PyYAML: 3.10
22 |             PyZMQ: 13.0.0
23 |             ZMQ: 3.2.2
24 |             Apache Libcloud: 0.14.1
25 | ```
26 | 
27 | Check the official doc if you need setup instruction for salt and salt-cloud.
28 | Once that's done, you need to setup a provider. I created the following YAML file
29 | 
30 | ```yaml
31 | runabove:
32 |   identity_url: https://auth.runabove.io/v2.0/tokens
33 |   compute_name: nova
34 |   compute_region: #THE-REGION#
35 |   service_type: compute
36 |   tenant: '#THE-TENANT#'
37 |   user: '#your-email@test.tld#'
38 |   password: #S3cr37Pa55w0rd#
39 |   provider: openstack
40 |   networks:
41 |     - fixed:
42 |     - #NETWORK-UUDI#
43 | ```
44 | 
45 | Everything that's wrapped in "#" needs to be configured for your account, here is how to get the information. First, get some command line tools:
46 | 
47 | ```
48 | sudo pip install python-novaclient.
49 | ```
50 | 
51 | Once that's done, go in the manager, in OpenStack Horizon, under __Access & Security__ and finally under __API Access__. Download the __OpenStack RC file__. Save it on your box, source it and enter your password. It's safe it comes from runabove.
52 | 
53 | ```
54 | source /home/jsb/openstackrc
55 | Please enter your OpenStack Password:
56 | ```
57 | 
58 | Now we are ready to gather the information to complete de provider setup:
59 | 
60 |  * #THE-REGION#:  run "nova endpoints". In the nova table you will find the region, mine looks like "BHS-1"
61 |  * #THE-TENANT#:  run "nova credentials", at the end of the table, you should see "name": "00000000" where 000000 is a bunch of number. This can also be seen in the manager, under current project. Make sure this is between quotes in your config file or it will not work.
62 |  * #NETWORK-UUDI#: run "nova network-list" and grab what's in the id column, that will be your static network. In my case, there is only one and it's labelled "Ext-Net".
63 | 
64 | Once that's done, the only thing left is to create vm image profiles. Im using these:
65 | 
66 | ```
67 | cat cloud.profiles.d/runabove.conf
68 | high-cpu:
69 |   provider: runabove
70 |   size: pci2.d.c1
71 |   deploy: False
72 | 
73 | high-mem:
74 |   provider: runabove
75 |   size: pci2.d.r1
76 |   deploy: False
77 | 
78 | ubuntu-lts:
79 |   image: Ubuntu 12.04
80 |   extends: high-cpu
81 | ```
82 | 
83 | You can run nova flavor-list to see what size are available and nova image-list for the OS. In both case, the configuration is expecting what's in the Name column.
84 | 
85 | Once you are all set, spin up a new instance:
86 | 
87 | ```
88 | salt-cloud -p #the-cloud-profile-you-chose# #the-instance-name#
89 | ```
90 | 
91 | Happy automated deployment folks!
92 | 


--------------------------------------------------------------------------------
/en/_posts/2014-04-22-how-to-store-your-backup-with-duplicity-and-openstack-swift.markdown:
--------------------------------------------------------------------------------
 1 | ---
 2 | layout: post
 3 | title: "How to store your backup with duplicity and Openstack Swift?"
 4 | categories: Object-Storage
 5 | lang: en
 6 | author: VincentCasse
 7 | ---
 8 | 
 9 | Duplicity is an open source tool for backing up your files. You can find more information on the official [website](http://duplicity.nongnu.org/).
10 | 
11 | Since version 0.6.22, Swift has been on the list of available back-ends. So you can use Duplicity to send your backup on RunAbove object storage.
12 | 
13 | # 1. Preparation
14 | 
15 | ## Download Duplicity
16 | 
17 | Download Duplicity with version 0.6.22 or later. Packaged versions are available for the most widely known distributions.
18 | 
19 | ## Get missing information
20 | 
21 | To connect to your RunAbove object storage, you will need to have your login, password and tenant name. This information can be found in __Openstack Horizon__ manager below __current project__
22 | 
23 | ![](https://lb1049.pcs.ovh.net/v1/AUTH_e17900908d244c4bb80525f0c0d3a227/public/access-to-your-object-storage-with-cyberduck.html/tenant_name.png)
24 | 
25 | ## Create a new container
26 | 
27 | RunAbove object storage allows you to create distinct areas called __containers__ to store your files. It's good practice to use a specific backup container. You can create it in your [control panel](https://cloud.runabove.com/#/add).
28 | 
29 | Under __What do you want to add?__, select _A storage_, then define your container name and geographical region.
30 | 
31 | # 2. Ready to backup?
32 | 
33 | The last step before starting your backup is to define your account information for Duplicity. You must define these environment variables: 
34 | 
35 |  * SWIFT_USERNAME: your username
36 |  * SWIFT_PASSWORD: your password
37 |  * SWIFT_AUTHURL: https://auth.runabove.io:443/v2.0
38 |  * SWIFT_AUTHVERSION: 2
39 |  * SWIFT_TENANTNAME: your tenant name
40 |  * SWIFT_REGIONNAME: (optional) region where you want to store backup (BHS-1, SBG-1...) (Available in duplicity>=0.7.02)
41 | 
42 | Finally, you can back up the __configuration__ folder in your __backup__ container.
43 | 
44 | ```
45 | duplicity configuration/ swift://backup
46 | ```
47 | 


--------------------------------------------------------------------------------
/en/_posts/2014-04-22-how-to-use-cyberduck-with-openstack-swift.markdown:
--------------------------------------------------------------------------------
 1 | ---
 2 | layout: post
 3 | title: "How to use Cyberduck with Openstack Swift?"
 4 | categories: Object-Storage
 5 | lang: en
 6 | author: VincentCasse
 7 | ---
 8 | 
 9 | To use RunAbove object storage, you can code integration into your software.  However, you will sometimes need to access your object storage without using your software. Cyberduck (available on Windows and Mac) is an application for accessing and managing your object storage, such as an FTP
10 | 
11 | # 1. Preparation
12 | 
13 | ## Download Cyberduck
14 | 
15 | Download the latest version of Cyberduck at [cyberduck.io](http://cyberduck.io) and install it.
16 | 
17 | Cyberduck is compatible with RunAbove from version 4.4.4. If you have version 4.4.3, you need to change the update channel to beta version. You can change the channel in the __Preferences__ menu, under the __Update__ tab. Change _Release_ to _beta_ and click on __Check for Update Now__
18 | 
19 | ## Get missing information
20 | 
21 | To connect to your RunAbove object storage, you will need to have your login, password and tenant name. This last information can be found in __OpenStack Horizon__ below __current project__
22 | 
23 | ![](https://lb1049.pcs.ovh.net/v1/AUTH_e17900908d244c4bb80525f0c0d3a227/public/access-to-your-object-storage-with-cyberduck.html/tenant_name.png)
24 | 
25 | # 2. Connection
26 | 
27 | ![](https://lb1049.pcs.ovh.net/v1/AUTH_e17900908d244c4bb80525f0c0d3a227/public/access-to-your-object-storage-with-cyberduck.html/conf_cyberduck.png)
28 | 
29 |  * Click on the __Open Connection__ button and select __Openstack Swift (keystone)__.
30 |  * Type _auth.runabove.io_ in the __Server__ field, your username in the __Username__ field and your password in... the __Password__ field!
31 |  * Submit form by clicking on __Connect__
32 |  * Type your tenant name and click on __Login__
33 | 
34 | ![](https://lb1049.pcs.ovh.net/v1/AUTH_e17900908d244c4bb80525f0c0d3a227/public/access-to-your-object-storage-with-cyberduck.html/cyberduck.png)
35 | 
36 | Congrats! You can now manage your objects, such as dragging and dropping files, or deleting folders.
37 | 


--------------------------------------------------------------------------------
/en/_posts/2014-04-22-how-to-use-vagrant-with-openstack.markdown:
--------------------------------------------------------------------------------
 1 | ---
 2 | layout: post
 3 | title:  "How to use vagrant with Openstack?"
 4 | categories: Instances
 5 | author: Jean Sébastien Bruneau
 6 | lang: en
 7 | ---
 8 | 
 9 | Can this be done? Yup!
10 | (you do need a recent fully functioning vagrant installation but if you are here, chances are that you do. If not, head to [http://www.vagrantup.com/](http://www.vagrantup.com).
11 | 
12 | # Prerequisites:
13 | 
14 | Get started, practice spining up local machine and get enlightened! Once you are done, keep on reading)
15 | 
16 | First, setup an ssh key via the runabove control panel. We will need that to connect into the instance once it's setup.
17 | 
18 | In OpenStack Horizon, under __Access & Security__, then under __Key Pairs__ and finally clicking the import Key Pair button gives instruction on how to generate and import a key.
19 | 
20 | ![](http://getoutofthecube.com/public/runabove-vagrant/1.PNG)
21 | 
22 | # Vagrant installation
23 | 
24 | Next, hit [https://github.com/cloudbau/vagrant-openstack-plugin](https://github.com/cloudbau/vagrant-openstack-plugin). The doc should get you going pretty fast. Only 2 commands are needed:
25 | 
26 | ```
27 | vagrant plugin install vagrant-openstack-plugin
28 | vagrant box add dummy https://github.com/cloudbau/vagrant-openstack plugin/raw/master/dummy.box
29 | ```
30 | 
31 | Once you are done, it's time to build a Vagrantfile, you can use this as a starting point:
32 | 
33 | ```
34 | Vagrant.configure("2") do |config|
35 |   config.vm.box = "dummy"
36 | 
37 |   # Make sure the private key from the key pair is provided
38 |   config.ssh.private_key_path = "/path/to/your/id_rsa"
39 | 
40 |   config.vm.provider :openstack do |os|
41 |     os.username     = "[your-runabove-username]"
42 |     os.api_key      = "[yourS3cre7pa55w0rd]"
43 |     os.flavor       = /[name-of-the-instance-model]/
44 |     os.image        = /[name-of-the-desired-os]/
45 |     os.endpoint     = "https://auth.runabove.io/v2.0/tokens"
46 |     os.keypair_name = "[name-of-the-key-you-uploaded]"[/
47 | 
48 |     os.ssh_username = "admin"
49 |     os.network      = "Ext-Net"
50 |   end
51 | end
52 | ```
53 | 
54 | Replace everything between the tags [] with your information (including the square braquets, you don't need them). Don't forget to add your provisioner stuff in there. You probably want to use a shell provisioner to bootstrap your favorite DevOps tool.
55 | 
56 | # And deploy vagrant inside openstack
57 | 
58 | Once you are happy with the configuration simply do a:
59 | 
60 | ```
61 | vagrant up --provider=openstack
62 | ```
63 | 
64 | Well that's it! you now have a very powerfull dev box!
65 | 


--------------------------------------------------------------------------------
/en/_posts/2014-05-13--how-to-optimize-upload-with-openstack-swift.markdown:
--------------------------------------------------------------------------------
 1 | ---
 2 | layout: post
 3 | title: "How to optimize uploads with Openstack Swift"
 4 | categories: Object-Storage
 5 | lang: en
 6 | author: gierschv
 7 | ---
 8 | 
 9 | OpenStack Swift allows you to store objects with a non-limited size by splitting them in [small segments](http://docs.openstack.org/developer/swift/overview_large_objects.html).
10 | 
11 | When a Swift client processes a request to upload an object (or a segment of an object), the Swift proxy determines the Swift storage node using a hash of the object name. Therefore, there is  a high probability that the segments will be stored in several storage nodes, which allow you to write your object(s) at an incredible speed.
12 | 
13 | Here is an example using a Run Above instance, uploading a big object (10Gio) using the [official command line client
14 | (python-swiftclient)](https://github.com/openstack/python-swiftclient) on
15 | Ubuntu or Debian:
16 | 
17 | 1 - Install the client
18 | ----------------------
19 | 
20 |     apt-get install python-pip
21 |     pip install python-keystoneclient python-swiftclient
22 | 
23 | 2 - Get your credentials
24 | ------------------------
25 | 
26 | Set your credentials in your environment using the [Open RC
27 | file](https://manager.runabove.com/horizon/project/access_and_security/api_access/openrc/)
28 | that you can download using the horizon dashboard.
29 | 
30 |     source XXXXXXX-openrc.sh
31 | 
32 | 3 - Example
33 | -----------
34 | 
35 | Upload into the "backups" container a 10 Gio file in 100 Mio parts using 100
36 | simultaneous connections:
37 | 
38 |     dd if=/dev/random of=10Gio.dat bs=$(( 2 ** 20 )) count=1024
39 |     swift upload --segment-size $(( 2 ** 20 * 100 )) --segment-threads 100
40 |     backups 10Gio.dat
41 | 
42 | 4 - Measure
43 | -----------
44 | 
45 | You can measure the upload using iftop, as shown below:
46 | ![Upload](https://pbs.twimg.com/media/BmO1wd6CAAAXSr4.png:large)
47 | 


--------------------------------------------------------------------------------
/en/_posts/2014-05-16-how-to-create-a-windows-instance.markdown:
--------------------------------------------------------------------------------
 1 | ---
 2 | layout: post
 3 | title:  "How to create a Windows instance?"
 4 | categories: Instances
 5 | author: VincentCasse
 6 | lang: en
 7 | ---
 8 | Windows instances are available inside RunAbove offers. How create Windows instances and how to use it?
 9 | 
10 | # Open your manager
11 | 
12 | Open RunAbove [https://cloud.runabove.com](https://cloud.runabove.com) with your login details.
13 | 
14 | ![Login screenshot](https://community.runabove.com/public/files/nKzJMRNEXydMmE3rrYCc.png)
15 | 
16 | # Add a new Windows instance
17 | 
18 | Click on __Add__ in the left-hand menu and choose to add __An instance__.
19 | 
20 | Fill in the form with your custom configuration:
21 |  * Image with _Windows Server 2012 R2_
22 |  * Region is the area where the instance is stored
23 |  * Template is the hardware profile you want
24 | 
25 | ![](https://community.runabove.com/public/files/deDLcP1otmuvLebRIAsv.png)
26 | 
27 | # Your Windows instance is ready
28 | 
29 | When the status of your instance is _ACTIVE_, you can open a screen on your instance. ![](https://community.runabove.com/public/files/2KT5xUbFFl4siIEi409b.png)
30 | You can configure your account inside Windows: localization information, contract agreements and account credentials. Now, your Windows instance is ready! You could use it with VNC console or [configure a _Remote Desktop_ access](/kb/en/instances/how-to-configure-remote-desktop-on-windows-server.html).
31 | 
32 | ![](https://community.runabove.com/public/files/bMkjjFn0pzyMtBvaHFyY.png)


--------------------------------------------------------------------------------
/en/_posts/2014-05-19-import-a-custom-image-in-your-runabove-account.markdown:
--------------------------------------------------------------------------------
 1 | ---
 2 | layout: post
 3 | title:  "Import a custom image in your RunAbove Account"
 4 | categories: Instances
 5 | author: NicolasLM
 6 | lang: en
 7 | ---
 8 | By default, RunAbove proposes different operating systems. If you need to launch an instance of a particular operating system, you can add an image very easily to your RunAbove account.
 9 | 
10 | # How do you add a custom operation system?
11 | 
12 | You just need to go to [OpenStack Horizon](https://cloud.runabove.com/horizon), in the "__Image__" tab and then, click on "__Create Image__". A pop-up will ask you for a few details about the system that you want to create and where to find the image itself.
13 | 
14 | ![Control panel screenshot](https://community.runabove.com/public/files/r84vLoKPpLjvd9uHnjBp.png)
15 | 
16 |  * The __name__ and __description__ should describe the system you want to upload.
17 |  * The __image source__ can be a public location on the web or a local file on your computer.
18 |  * The __format__ describes the virtual disk type of the image. The most common ones are Raw and Qcow2.
19 |  * The others parameters are optional.
20 | 
21 | Just click on "__Create Image__", if you create an image from a local file it will be uploaded, otherwise it will be fetched from the location you specified.
22 | 
23 | You can now find your custom system in the “__Image__” field when you launch instances. If you need a customized image you can [easily create it for RunAbove](/kb/en/instances/how-to-create-a-custom-image-for-runabove.html).
24 | 


--------------------------------------------------------------------------------
/en/_posts/2014-05-20-how-to-configure-remote-desktop-on-windows-server.markdown:
--------------------------------------------------------------------------------
 1 | ---
 2 | layout: post
 3 | title:  "How to configure 'Remote Desktop' on your Windows Instance?"
 4 | categories: Instances
 5 | author: VincentCasse
 6 | lang: en
 7 | ---
 8 | 
 9 | You already have a Windows instance, but you want remote desktop access directly within your account. You need to open a port inside the firewall and configure Windows to authorize RDP access. What is RDP? A Windows protocol for sharing desktop screens between machines over the internet. With this protocol, you can control other computers or servers in the same way as with your own personal machine.
10 | 
11 | If you don't have a Windows instance, you should read "[how to create a Windows instance?](/kb/en/instances/how-to-create-a-windows-instance.html)"
12 | 
13 | # Open RDP port in firewall
14 | 
15 | Your instance is protected by an external firewall. By default, only ports 80 (HTTP) and 443 (HTTPS) are open and you need to open port 3389 to authorize the RDP protocol. The firewall rules can be edited in OpenStack Horizon, using the manager, under the _Access & Security_ tab.
16 | 
17 | If you haven't replaced your security group since your instance was launched, your security group will be _default_.
18 | 
19 |  * Click on _Edit Rules_
20 |  * Then on _Add Rules_
21 |  * Choose _RDP_ inside Rule field.
22 | 
23 | By default, port 3389 will be open to the entire internet and you can limit it to a specific IP. For example, if you want to limit access to the IP 127.0.0.1, simply enter 127.0.0.1/32 in CIDR field.
24 | 
25 | ![Control panel screenshot](https://community.runabove.com/public/files/taBGpST1Y4zvfPEEs66y.png)
26 | 
27 | # Authorize RDP access inside a Windows instance
28 | 
29 | Launch your Windows instance and open a console. To configure the RDP access, open the _Server Manager_ and click on _Local Server_ in the left-hand menu. You will see the _Remote Desktop_ status and if it's disabled, click on it to edit the configuration.
30 | 
31 | Choose _Allow remote connections to this computer_. If your RDP client doesn't use Network Level Authentication, or if this feature is not available on your network, be sure the field _Allow connections only from computers running Remote Desktop with Network Level Authentication_, is not selected.
32 | 
33 | # Open an RDP client
34 | 
35 | You can now open your favorite RDP client. On Linux, you could use rdesktop.
36 | 
37 | ```bash
38 | rdesktop 127.0.0.1
39 | ```
40 | 


--------------------------------------------------------------------------------
/en/_posts/2014-06-17-how-to-install-docker-on-runabove.markdown:
--------------------------------------------------------------------------------
 1 | ---
 2 | layout: post
 3 | title:  "How to install Docker on RunAbove?"
 4 | categories: Instances
 5 | author: KDevroede
 6 | lang: en
 7 | ---
 8 | 
 9 | Docker is a great tool to simplify the deployment of applications. It separates development from deployment, allowing you to run your application inside containers with complete resource isolation.
10 | 
11 | As RunAbove supports cloud-init post-installation, we can take advantage of this to easily install docker when spawning an instance.
12 | 
13 | # Launch host instance:
14 | 
15 | From [OpenStack Horizon](https://cloud.runabove.com/horizon/), click on _Instances_ panel and then on _Launch instance_ button. This guide is tested on Ubuntu, Debian and CoreOS, but you can test other operating system.
16 | 
17 | ![Control panel screenshot](http://community.runabove.com/public/files/LzBsy2lfpeVYuJv03ii5.png)
18 | 
19 | Don't forget to add a network interface into _Networking_ tab!
20 | 
21 | # Add post-installation script to deploy docker:
22 | 
23 | Next, go to the _Post-Creation_ tab and add the command below into _Customization script_ field.
24 | 
25 | ```bash
26 | #include https://get.docker.io
27 | ```
28 | 
29 | ![Control panel screenshot](http://community.runabove.com/public/files/7MPJC8i8FL2bXpFd3ax0.png)
30 | 
31 | Click on _Launch_ button to create your Docker platform.
32 | 
33 | # Use Docker
34 | 
35 | Once your instance is spawned, you can ssh into it and start using Docker.
36 | 
37 | ```bash
38 | admin@docker:~$ sudo docker version
39 | Client version: 1.0.0
40 | Client API version: 1.12
41 | Go version (client): go1.2.1
42 | Git commit (client): 63fe64c
43 | Server version: 1.0.0
44 | Server API version: 1.12
45 | Go version (server): go1.2.1
46 | Git commit (server): 63fe64c
47 | ```
48 | 
49 | If you want to learn more about Docker and how to use it, you can follow this guide:
50 | [http://www.docker.com/tryit/](http://www.docker.com/tryit)
51 | 
52 | You can see also [how to install CoreOS on RunAbove](/kb/en/instances/how-to-deploy-core-os-on-runabove.html) to deploy a very small operating system below Docker containers.
53 | 


--------------------------------------------------------------------------------
/en/_posts/2014-06-18-upload-your-first-object-inside-swift.markdown:
--------------------------------------------------------------------------------
 1 | ---
 2 | layout: post
 3 | title: "Upload your first object inside Openstack Swift"
 4 | categories: Object-Storage
 5 | lang: en
 6 | author: VincentCasse
 7 | ---
 8 | 
 9 | You have got a new Runabove account and you want to use object storage but you don't know how! Take five minutes to learn it!
10 | 
11 | # Some prerequisites:
12 | 
13 | Before all, you need to have a RunAbove account with valid credentials, a web browser, python and pip (python packager) installed on your computer... Yes, that's all!
14 | 
15 | # Installation:
16 | 
17 | To communicate with OpenStack APIs proposed by RunAbove, you need to install official OpenStack clients:
18 | 
19 | ```
20 | pip install python-swiftclient python-keystoneclient
21 | ```
22 | 
23 | Now you can begin to store your data!
24 | 
25 | # How to authenticate?
26 | 
27 | To be authenticated inside your Object Storage, you need to define some environment variables with your account credentials.
28 | 
29 | The simpliest way is to download a script to do it. You can find it in your control panel, in OpenStack Horizon.
30 | Then go into _Access & Security_ panel, then into _API Access_ tab. Finally, click on _Download OpenStack RC File_.
31 | 
32 | ![](http://community.runabove.com/public/files/JvEL9P7dJKRRpPDFEPRK.png)
33 | 
34 | Launch this script and enter your RunAbove password:
35 | 
36 | ```
37 | source 13370042-openrc.sh
38 | ```
39 | 
40 | Select the region you want to work in:
41 | 
42 | ```
43 | export OS_REGION_NAME="SBG-1"
44 | ```
45 | 
46 | To verify if you are authenticated, you can launch the next request and you will get some account metadata.
47 | 
48 | ```
49 | swift stat
50 | ```
51 | 
52 | # Upload your first object:
53 | 
54 | To upload _the_object.txt_ file into your Object Storage, you can use this command:
55 | 
56 | ```
57 | swift upload container_name path_to_the_object.txt
58 | ```
59 | 
60 | You can verify that your file is in container_name with:
61 | 
62 | ```
63 | swift list container
64 | ```
65 | 
66 | # Interact with your object:
67 | 
68 | You can download content of your object with:
69 | 
70 | ```
71 | swift download container_name path_to_the_object.txt
72 | ```
73 | 
74 | When you need to delete your object, you can use this request:
75 | 
76 | ```
77 | swift delete container_name path_to_the_object.txt
78 | ```
79 | 
80 | # How to continue to discover Object Storage?
81 | 
82 | To begin, you can continue to discover features of your Object Storage with documentation of the client:
83 | 
84 | ```
85 | swift help
86 | ```
87 | 
88 | Now you can think about direct integration of Object Storage in your applications and use officials SDKs or directly with HTTP requests to OpenStack APIs.
89 | 


--------------------------------------------------------------------------------
/en/_posts/2014-07-07-how-to-configure-owncloud-7-with-swift.markdown:
--------------------------------------------------------------------------------
 1 | ---
 2 | layout: post
 3 | title: "How to configure Owncloud 7 with Openstack Swift?"
 4 | categories: Object-Storage
 5 | lang: en
 6 | author: ArnaudJost
 7 | ---
 8 | 
 9 | Owncloud is a software application which allows you to host, sync and share files, hosted on your own dedicated or virtual server.
10 | 
11 | The past few releases of OwnCloud allo users to host files on external storage, using a module. For example, you can use FTP or Openstack swift as a second backend storage.
12 | 
13 | With Owncloud 7, you can now use Openstack swift as [u]main storage[/u], and benefit with fast and secure storage from RunAbove without local storage problem (drive failure..).
14 | 
15 | 
16 | # Prerequistes :
17 | 
18 |  * Working Owncloud instance, freshly installed on your server (you can donwload and find help about Owncloud here : [https://owncloud.org/install/](https://owncloud.org/install/)
19 |  * Your tenant name is your project number. You can find it in [OpenStack Horizon](https://cloud.runabove.com/horizon/).
20 | 
21 | # Configure Owncloud 7 to use Runabove storage:
22 | 
23 | You have to manually configure Openstack storage in Owncloud's config file. You'll find it in Owncloud's http storage directory: config/config.php.
24 | 
25 | Edit this file, and add this new configuration element in $CONFIG array :
26 | 
27 | ```php
28 | 'objectstore' => array(
29 |     'class' => 'OC\\Files\\ObjectStore\\Swift',
30 |     'arguments' => array(
31 |         'username' => 'myusername@mymail.com', // Runabove username
32 |         'password' => 'mypassword', // Runabove password
33 |         'container' => 'owncloud', // Container name. Ownclound store files using it's own metadata,
34 |         // so, keep a container only for Owncloud use.
35 |         'autocreate' => true, // Create the container if it does not exist. default is false
36 |         'region' => 'SBG-1', // Region where you want to store files
37 |         'url' => 'https://auth.Runabove.io/v2.0', // Runabove identity endpoint
38 |         'tenantName' => '1234567', // project name
39 |         'serviceName' => 'swift', // service name, should be 'swift' on Runabove[
40 |     ),
41 | )
42 | ```
43 | 
44 | Then, just reload Owncloud on your favorite browser. Every users now store files on Runabove instead of using local storage. Please note that local storage is not longer used, so, please use a fresh install of Owncloud 7 or backup your files before.
45 | 


--------------------------------------------------------------------------------
/en/_posts/2014-07-09-what-is-object-storage.markdown:
--------------------------------------------------------------------------------
 1 | ---
 2 | layout: post
 3 | title: "What is Object Storage?"
 4 | categories: Object-Storage
 5 | lang: en
 6 | author: BaQs
 7 | ---
 8 | 
 9 | RunAbove have an Object Storage offer to manage huge quantity of data. Is it good for you?
10 | 
11 | # Definitions
12 | 
13 | First of all, the most important: an object storage __IS NOT a file system:__ it has no hierarchy!
14 | 
15 | Imagine yourself having an huge (unlimited) shelf, with a lot of drawers.
16 | You can [PUT](http://docs.openstack.org/api/openstack-object-storage/1.0/content/PUT_createOrReplaceObject__v1__account___container___object__storage_object_services.html) anything in any drawer, [DELETE](http://docs.openstack.org/api/openstack-object-storage/1.0/content/DELETE_deleteObject__v1__account___container___object__storage_object_services.html) it afterwards, or [GET](http://docs.openstack.org/api/openstack-object-storage/1.0/content/GET_getObject__v1__account___container___object__storage_object_services.html) its content.
17 | 
18 | You can provide access publicly to your shelf via HTTP links.
19 | 
20 | Using RunAbove Object Storage, you have many shelves like that. We call them containers. Moreover, anything you store is replicated 3 times, you won't loose it.
21 | 
22 | # What is it good for ?
23 | 
24 | Basically, anything you want to store & share. An object storage is a distribution platform. Upload it once and it can be available directly via http. Millions of downloads can occur, we will handle it.
25 | 
26 | If you actually use a web application to serve file, you do not need it any more. That's what an object storage is for. You can make objects expire after some time, share them for a period, add metadata that web browsers understand.
27 | 
28 | You want to host a static website ? It's PERFECT!
29 | 
30 | Privately, you can store any file that need to be accessed by others applications/scripts or users, or as part of a process.
31 | 
32 | ## For instance:
33 | You store a big video, then download it on another server to re-encode it, then push it back to share it with a lot of people.
34 | 
35 | There are tons of examples like that, and there is no limit !
36 | 
37 | # Where/how to begin ?
38 | 
39 | RunAbove runs Openstack Swift, and makes it simple to use:
40 | 
41 | ## Use OpenStack Horizon
42 | 
43 | Some screenshots to guide you through (from simple mode to Horizon)
44 | ![](https://community.runabove.com/public/files/irKoAPPu6y6JZfRoEZc5.png)
45 | ![](https://community.runabove.com/public/files/FJksBNU8geDPNs0kRHiy.png)
46 | ![](https://community.runabove.com/public/files/MUigXnPlL4xR4sH3SsCy.png)
47 | 
48 | ## Use any language of your choice:
49 | 
50 |  * [Python](https://github.com/runabove/python-runabove)
51 |  * [Go](https://github.com/ncw/swift)
52 |  * Java with [JOSS](http://joss.javaswift.org)
53 | 
54 | Long story short, anything that is compatible with OpenStack Swift will work.
55 | Checkout all [openstack available SDKs](https://wiki.openstack.org/wiki/SDKs) _C, Clojure, Erlang, Go, Java, Android, JavaScript, .Net, Node.js, Perl, PHP, Python, Ruby_
56 | 
57 | You can even use [Owncloud](/kb/en/object-storage/how-to-configure-owncloud-7-with-swift.html), [Duplicity](/kb/en/object-storage/how-to-store-your-backup-with-duplicity-and-openstack-swift.html)or even [CyberDuck](/kb/en/object-storage/how-to-use-cyberduck-with-openstack-swift.html).
58 | Or if you're addicted to Command Line, you can also use [CURL](http://docs.openstack.org/api/openstack-object-storage/1.0/content/examples.html).
59 | 
60 | As a last link, OpenStack Swift documentation: http://docs.openstack.org/developer/swift/
61 | 


--------------------------------------------------------------------------------
/en/_posts/2014-09-09-how-to-schedule-deletion-of-objects.markdown:
--------------------------------------------------------------------------------
 1 | ---
 2 | layout: post
 3 | title: "How to schedule deletion of objects"
 4 | categories: Object-Storage
 5 | lang: en
 6 | author: ArnaudJost
 7 | ---
 8 | 
 9 | Sometimes, you need to delete one ore more object at a specific time.
10 | 
11 | For example, if you want to manage backups and delete them when older than X month, if  you want to create a cache for an application, or just because the data itself has a specific lifetime. It's very difficult to do this by hand : you have to list objects, check dates, and delete if needed...
12 | 
13 | Openstack Swift includes a very cool feature which is a nice solution to this problem : X-Delete-* header. You just have to push this header associated with a date on your object, and swift will do the job for you. Simple & Efficient.
14 | 
15 | # Prerequisites :
16 | 
17 |  * Python installed on your computer (https://www.python.org/)
18 |  * Openstack swift client (https://github.com/openstack/python-swiftclient) or curl on unix.
19 | 
20 | # How it works :
21 | 
22 | An internal process parses objects on your account, and checks if the header X-Delete-At exists. If the header exists, it deletes the object if it's time, without any other intervention.
23 | 
24 | 
25 | Please note that you'll always find the same header on your object: X-Delete-At, but you can push another header on your object : X-Delete-After (delete in X seconds). X-Delete-After is converted in X-Delete-At when you push it on your object.
26 | 
27 | ```
28 | X-Delete-After: delete in X seconds
29 | X-Delete-At: delete at this date, in unix epoch format
30 | ```
31 | 
32 | # Let's delete an object automatically
33 | 
34 | First, get epoch time (or get the number of seconds that you need, if using X-Delete-After):
35 | 
36 | * Using http://www.epochconverter.com/
37 | * On linux : date +%s
38 | 
39 | Then, post the header on your object.
40 | 
41 | With curl :
42 | 
43 | ```bash
44 | curl -X POST \
45 |      -H 'X-Delete-After: 3600'\
46 |      -H 'X-Auth-Token: 123' \
47 |      https://storage.bhs-1.runabove.io/default/image.jpg
48 | 
49 | curl -X POST\
50 |      -H 'X-Delete-At: 1401268563'\
51 |      -H 'X-Auth-Token: 123'\
52 |      https://storage.bhs-1.runabove.io/default/image.jpg
53 | ```
54 | 
55 | With swift client :
56 | 
57 | ```bash
58 | swift -v -V 2.0 -A https://auth.runabove.io/v2.0 -U tenant:login -K pass post --header "X-Delete-After: 3600" container object
59 | swift -v -V 2.0 -A https://auth.runabove.io/v2.0 -U tenant:login -K pass post --header "X-Delete-At: 1401268563" container object
60 | ```
61 | 
62 | You can check if the header is correctly applied using swift client :
63 | 
64 | ```bash
65 | swift -v -V 2.0 -A https://auth.runabove.io/v2.0 -U tenant:login -K pass stat container object
66 | ```
67 | 
68 | Or with curl :
69 | 
70 | ```bash
71 | curl -X HEAD -H 'X-Auth-Token: 123' https://storage.bhs-1.runabove.io/default/image.jpg
72 | ```
73 | 
74 | You should see something like :
75 | 
76 | ```
77 | X-Delete-At: 1402647646
78 | ```
79 | 
80 | And it's already done ! You have nothing more to do, swift will delete the object on the chosen date.
81 | 
82 | # Conclusion :
83 | 
84 | With Openstack swift, it's very easy to create objects based on lifetime duration. With very few requests, you can set a destroy date and not be bothered with the deletion of old object.
85 | You can also easily develop a scalable cache without management of deletion.
86 | 


--------------------------------------------------------------------------------
/en/_posts/2014-09-24-foreman-openstack-multi-region.markdown:
--------------------------------------------------------------------------------
 1 | ---
 2 | layout: post
 3 | title:  "Manage a multi-region OpenStack infrastructure with Foreman"
 4 | categories: Instances
 5 | author: NicolasLM
 6 | lang: en
 7 | ---
 8 | 
 9 | Foreman is a tool that a allows to manage an infrastructure of servers easily.
10 | It is compatible with OpenStack so it can automatize the deployment of RunAbove
11 | instances.
12 | 
13 | Foreman uses a Ruby library called [fog](https://github.com/fog/fog) to be
14 | compatible with many providers. This library does the abstraction layer between
15 | Foreman and OpenStack.
16 | 
17 | In RunAbove we have an OpenStack cloud with two regions, `SBG-1` and `BHS-1`.
18 | This is handled correctly in fog, but Foreman does not allow to select the
19 | proper OpenStack region. Thus it fails with the message:
20 | 
21 |     Multiple regions available choose one of these 'SBG-1,BHS-1'
22 | 
23 | Until the Foreman developers update their software to use the multi-region 
24 | feature of fog, a quick patch can be made, allowing to set one region. Just 
25 | patch the file
26 | [openstack.rb](https://github.com/theforeman/foreman/blob/d21103bcf13b5981601be88330ce73dbe4a1ed77/app/models/compute_resources/foreman/model/openstack.rb#L104)
27 | line 104, and add:
28 | 
29 |     :openstack_region   => 'SBG-1'   ,
30 | 
31 | This will tell fog to only work on the `SBG-1` region. Restart Foreman and you
32 | will be able to work on a multi-region OpenStack cloud.
33 | 


--------------------------------------------------------------------------------
/en/_posts/2014-09-25-use-openstack-command-line-tools.markdown:
--------------------------------------------------------------------------------
 1 | ---
 2 | layout: post
 3 | title: "How to use OpenStack command line tools?"
 4 | categories: Instances
 5 | author: bartekzurawski
 6 | ---
 7 | 
 8 | OpenStack is a cloud computing software built with several modules (Nova,
 9 | Swift, Neutron...) interacting with each others. In this guide we will focus on
10 | how to use the command line clients of these modules.
11 | 
12 | OpenRC file
13 | -----------
14 | 
15 | To use any command line client, you need to load the `openrc` file. This file
16 | contains special environments variables which are used by command line clients
17 | to authenticate to the server where the service is running.
18 | 
19 | Let's start! To begin, go to the [OpenStack Horizon
20 | panel](https://cloud.runabove.com/horizon/project/access_and_security/), go to
21 | __Access & Security__ and switch tab to __API Access__. Finally __Download
22 | OpenStack RC File__ will allow you to retrieve the credentials needed to
23 | interact with OpenStack services.
24 | 
25 | The file that you downloaded, is a shell script. To load it, you can use the
26 | source command of your shell:
27 | 
28 |     source <openrc_file>
29 | 
30 | For security reasons your password is not stored in this file, so you will be
31 | prompted to enter your RunAbove password.
32 | 
33 | You can now check that the environment is correctly loaded, perform:
34 | 
35 |     env | grep OS_
36 | 
37 | As you can see your environment has been loaded correctly. Remind to reload
38 | this file each time you start a new shell.
39 | 
40 | Command line clients
41 | --------------------
42 | 
43 | ### Python pip
44 | 
45 | To use command line clients, you need to install them first. The most
46 | convenient way to do that is with `pip`, the standard tool for installing
47 | Python packages. On any Debian like operating system you can install `pip`
48 | with:
49 | 
50 |     sudo apt-get install python-pip
51 | 
52 | If you are familiar with Python Virtualenv, you can then create a new
53 | virtualenv and install the OpenStack clients in it, but this is not mandatory.
54 | 
55 | ### Installing OpenStack clients
56 | 
57 | OpenStack provides a [list of
58 | clients](https://wiki.openstack.org/wiki/OpenStackClients) you can install.
59 | Just enter the command below with the name of the client, for example:
60 | 
61 |     sudo pip install python-novaclient
62 | 
63 | ### Using the clients
64 | 
65 | In RunAbove there are two region, `BHS-1` and `SBG-1`. If you want get data
66 | from only one of them, you need to add the parameter `--os-region-name
67 | <region>` for example:
68 | 
69 |     nova --os-region-name BHS-1 list
70 |     glance --os-region-name SBG-1 image-list
71 | 
72 | It is also possible to define the region in an environment variable, just do:
73 | 
74 |     export OS_REGION_NAME=BHS-1
75 | 
76 | OpenStack clients have a useful help accessible with `help`, for example for
77 | nova:
78 | 
79 |     nova help
80 | 
81 | You can get the detailed usage of a subcommand with:
82 | 
83 |     nova help boot
84 | 
85 | You can also check the [online
86 | documentation](http://docs.openstack.org/cli-reference/content/) of all
87 | OpenStack clients.
88 | 


--------------------------------------------------------------------------------
/en/_posts/2014-09-26-update-bash-shellshock.markdown:
--------------------------------------------------------------------------------
 1 | ---
 2 | layout: post
 3 | title: "Protect your bash from Shellshock"
 4 | categories: Instances
 5 | author: NicolasLM
 6 | ---
 7 | 
 8 | On September 24th a critical security issue has been found in `bash`. The issue
 9 | is called
10 | [Shellshock](https://security-tracker.debian.org/tracker/CVE-2014-6271). Under
11 | certain circumstances, a remote attacker could execute commands on the system
12 | using this breach. Here is what to do to safely use RunAbove systems.
13 | 
14 | New instances
15 | -------------
16 | 
17 | Images on RunAbove has been updated with the latest security fix. Each new
18 | instance will not be vulnerable anymore. You do not need to do anything else.
19 | 
20 | Already existing instances
21 | --------------------------
22 | 
23 | For instances launched before September 26th it is very important to update
24 | `bash`.
25 | 
26 | By now all distribution vendors have fixed the issue in the `bash` package. To
27 | benefit from the fix you only need to update your system with the package
28 | manager.
29 | 
30 | ### Debian and Ubuntu
31 | 
32 | On Debian and Ubuntu you can update your system with `apt`:
33 | 
34 |     sudo apt-get update && sudo apt-get upgrade
35 | 
36 | ### Fedora and CentOS
37 | 
38 | On Fedora and CentOS you can update your system with `yum`:
39 | 
40 |     sudo yum update
41 | 
42 | Other systems
43 | -------------
44 | 
45 | If you feel like compiling the latest version of `bash` from sources you can
46 | fetch the tarball and run the build with:
47 | 
48 |     wget http://ftp.gnu.org/gnu/bash/bash-4.3.tar.gz
49 |     tar -xf bash-4.3.tar.gz
50 |     cd bash-4.3
51 |     make
52 | 
53 | You can then install it:
54 | 
55 |     make install
56 | 


--------------------------------------------------------------------------------
/en/_posts/2014-10-06-power8-features.markdown:
--------------------------------------------------------------------------------
 1 | ---
 2 | layout: post
 3 | title: "How to use Power8 features"
 4 | categories: Instances
 5 | author: NicolasLM
 6 | ---
 7 | 
 8 | Power8 is a new generation of processors designed to improve performances of 
 9 | parallelized computations. This guide will explain how to customize the 
10 | features of the processor on the go.
11 | 
12 | How Power8 processors are different?
13 | ------------------------------------
14 | 
15 | Power8 allows you to changes the specifications of the system on the go. You 
16 | can adapt the characteristics of the CPU to your needs.
17 | 
18 | Customize the features
19 | ----------------------
20 | 
21 | Running the command `ppc64_cpu` as root you can manage the Power8 features.
22 | 
23 | ### Threads
24 | 
25 | If you application use a reduced number of instructions or do not do expensive 
26 | IO, you can benefit from disabling threads. For example, set 8 threads per 
27 | core:
28 | 
29 |     sudo ppc64_cpu --smt=8
30 | 
31 | Completely disable threads:
32 | 
33 |     sudo ppc64_cpu --smt=off
34 | 
35 | ### Cores
36 | 
37 | Our Power8 processor has 22 cores, as you can check with:
38 | 
39 |     sudo ppc64_cpu --cores-present
40 |        - Number of cores present = 22
41 | 
42 | You can disable cores on the go:
43 | 
44 |     sudo ppc64_cpu --cores-on=8
45 |     sudo ppc64_cpu --cores-on
46 |        - Number of cores online = 8
47 | 
48 | Do not forget to buy a second monitor dedicated to htop, otherwise you will not 
49 | see any process:
50 | 
51 | ![Power8 htop](/kb/images/2014-10-06-power8/htop.png)
52 | 


--------------------------------------------------------------------------------
/en/_posts/2014-10-16-how-to-fix-sslv3-poodle-vulnerability-nginx-apache-on-ubuntu-14.04.markdown:
--------------------------------------------------------------------------------
 1 | ---
 2 | layout: post
 3 | title: "How to fix SSLv3 POODLE vulnerability in Nginx and Apache on Ubuntu 14.04.1"
 4 | categories: Security
 5 | author: krnflake
 6 | ---
 7 | **Introduction**:
 8 | ---
 9 | The recently published [Poodle attack by Google](https://www.openssl.org/~bodo/ssl-poodle.pdf)
10 | forces a relapse of an encrypted connection to the long outdated SSLv3 protocol. For reasons of
11 | compatibility, almost all browsers still support this outdated protocol. This old protocol isn't
12 | really needed anymore. Hence the best protection is: just to turn it off. The worst
13 | that can happen is, that older browsers can't establish an encrypted connections, but
14 | this does only come into existence in individual cases. This certainly applies to the
15 | Internet Explorer 6, which is only rarely used. And who still uses the monster from
16 | time immemorial, has to contend with a lot of other problems. Web servers should actually
17 | support at least TLS 1.0.
18 | 
19 | **How to disable SSLv3 on Nginx**:
20 | ---
21 | 1) Find all virtualhost configuration files which use of the “ssl_protocols” directive:
22 | 
23 |     $ grep -R "ssl_protocols" /etc/nginx/sites-*
24 | 
25 | 2) Edit each file which we found in Step 1) that has the “ssl_protocols” directive:
26 | 
27 |     $ sudo nano /etc/nginx/sites-available/default
28 | 
29 | 3) Now find the following line:
30 | 
31 |     ssl_protocols SSLv3 TLSv1 TLSv1.1 TLSv1.2;
32 | 
33 | 4) And remove the option "SSLv3" so that the line will look like this:
34 | 
35 |     ssl_protocols TLSv1 TLSv1.1 TLSv1.2;
36 | 
37 | 5) In order to make the change effective restart Nginx:
38 | 
39 |     $ sudo service nginx reload
40 | 
41 | **How to disable SSLv3 on Apache**:
42 | ---
43 | 1) Edit Apache's SSL configuration:
44 | 
45 |     $ sudo nano /etc/apache2/mods-enabled/ssl.conf
46 | 
47 | 2) Find the following line:
48 | 
49 |     SSLProtocol all -SSLv2
50 | 
51 | 3) And add the option "-SSLv3" so that the line will look like this:
52 | 
53 |     SSLProtocol all -SSLv2 -SSLv3
54 | 
55 | 4) In order to make the change effective restart Apache:
56 | 
57 |     $ sudo service apache2 restart
58 | 


--------------------------------------------------------------------------------
/en/_posts/2014-10-16-how-to-install-gitlab.md:
--------------------------------------------------------------------------------
 1 | ---
 2 | layout: post
 3 | title: "How to install Gitlab on Ubuntu 14.04"
 4 | categories: Instances
 5 | author: DrOfAwesomeness
 6 | lang: en
 7 | ---
 8 | [Gitlab](https://about.gitlab.com/) Community Edition is a free and open-source git repository management and code collaboration tool. It provides an issue tracker, pull request system, and repository management system.
 9 | 
10 | 1. Installing Gitlab
11 | ================
12 | Installing Gitlab is a straightforward and easy process. Note that because RunAbove currently blocks outbound port 25 due to abuse, if you want your Gitlab instance to be able to send email, you'll need to install Postfix and [configure it to use another mail server as a relay](/kb/en/instances/how-to-relay-postfix-mails-via-smtp.gmail.com-on-ubuntu-14.04.html). To set up Gitlab, you'll need to download the official deb package and install it:
13 | 
14 | ```bash
15 | wget https://downloads-packages.s3.amazonaws.com/ubuntu-14.04/gitlab_7.3.2-omnibus-1_amd64.deb
16 | sudo dpkg -i gitlab_7.3.2-omnibus-1_amd64.deb
17 | ```
18 | 
19 | Please note that the `dpkg` command above may take up to 10 minutes to complete. After `dpkg` has finished, you'll need to edit the Gitlab configuration file with `sudo -e /etc/gitlab/gitlab.rb`. In the editor, change the `external_url` line to the URL you will be using to access Gitlab, which can be the IP address of your instance if you don't have a domain name pointed at it. After you've set the `external_url`, save the file and run `sudo gitlab-ctl reconfigure`. Congratulations, you have successfully installed Gitlab CE on your RunAbove instance!
20 | 
21 | 2. Configuring Users and Projects
22 | ============================
23 | So, now that you have successfully set up Gitlab CE on your instance, you'll probably want to add some users and projects. Go ahead and browse to the IP address or domain name of your instance. You'll be greeted with a sign in screen. The default username is `root` and the default password is `5iveL!fe`. Upon signing in, you'll immediately be prompted for a new password.
24 | 
25 | After updating your password, you'll be presented with your user dashboard. From here you can create a new project or group. If you want to make a new project, simply click on the New Project button, enter the project name, choose the project visibility, and hit the Create Project button. If you want to add more users to your Gitlab instance, you can do so by clicking the Admin Area icon (a large gear and two smaller gears) in the upper-right corner of your screen, and clicking on "New User". Please note that if you did not install Postfix and [configure it to use another mail server as a relay](/kb/en/instances/how-to-relay-postfix-mails-via-smtp.gmail.com-on-ubuntu-14.04.html), you will need to edit the user after creation to set the password.
26 | 
27 | Congratulations, you now have a working Gitlab CE instance! There are no limits to the number of projects you can create in Gitlab CE besides the limitations of the disk space on your RunAbove instance. If you want to learn more about Gitlab CE, be sure to check out the [documentation](http://doc.gitlab.com/ce/).
28 | 


--------------------------------------------------------------------------------
/en/_posts/2014-10-21-how-to-install-the-codebox-ide.md:
--------------------------------------------------------------------------------
 1 | ---
 2 | layout: post
 3 | title:  "How to install the Codebox IDE on Ubuntu 14.04"
 4 | categories: Instances
 5 | author: DrOfAwesomeness
 6 | lang: en
 7 | ---
 8 | 
 9 | The [Codebox IDE](https://github.com/CodeboxIDE/codebox) is the open-source 
10 | component of the [Codebox](https://www.codebox.io/) Cloud IDE service. It 
11 | provides developers with a cloud-based development code editor, terminal, and 
12 | file manager. This tutorial will show you how to set up the Codebox IDE on 
13 | Ubuntu 14.04.
14 | 
15 | ##1. Set up Node.js
16 | The Codebox IDE is written in Node.js, so we'll need to install the Node.js 
17 | runtime. The version of Node.js in the Ubuntu repositories is outdated, so 
18 | we'll be using the Nodesource repository to install Node.js. Note that we're 
19 | also installing the `build-essential` and `git` packages, as they are Codebox 
20 | IDE dependencies.
21 | 
22 | ```bash
23 | curl -sL https://deb.nodesource.com/setup | sudo bash -
24 | sudo apt-get install -y nodejs build-essential git
25 | ```
26 | 
27 | ## 2. Install and run the Codebox IDE
28 | Now that we have Node.js, it's time to install and run the Codebox IDE. First, 
29 | we need to install the `codebox` package with npm:
30 | 
31 | ```bash
32 | sudo npm install -g codebox
33 | ```
34 | 
35 | Next, since it's not a good idea to run the IDE as the `admin` or `root` user 
36 | (IDE users have terminal access), we'll add a user for it:
37 | 
38 | ```bash
39 | sudo adduser --disabled-password --gecos "Codebox IDE" codebox
40 | ```
41 | 
42 | Finally, we'll set up our workspace and run the Codebox IDE:
43 | 
44 | ```bash
45 | sudo -u codebox -i
46 | mkdir -p Workspace/your_project_name # or git clone <url> Workspace/your_project_name
47 | git init Workspace/your_project_name # skip this if you cloned from a git repository in the last command
48 | codebox run Workspace/your_project_name
49 | ```
50 | 
51 | Your IDE is now available at `http://your-instance-ip:8000`. If you are using 
52 | the default RunAbove firewall settings, you'll need to allow traffic on port 
53 | 8000.
54 | 
55 | From OpenStack Horizon, click on "Access & Security", and add a rule to the 
56 | default security group allowing ingress traffic to port 8000. Note that your 
57 | instance is currently open to the public. If you want to password-protect your 
58 | IDE, you can specify usernames and passwords as shown below.
59 | 
60 | ```bash
61 | # Run this as the codebox user
62 | codebox run Workspace/your_project_name -u user1:passwd1,user2:passwd2
63 | ```
64 | 
65 | **SECURITY NOTE:** The Codebox IDE currently does not provide a way to hash 
66 | passwords or hide them from the output of `ps ux`. Because of this, you should 
67 | use a unique, secure password to access the IDE. Additionally, if you are using 
68 | the Codebox IDE in a multi-user environment, you may want to avoid the internal 
69 | user system altogether and set up an authenticating reverse proxy.
70 | 
71 | If you don't want to leave your SSH window open the whole time the Codebox IDE 
72 | is running, you can run it in the background using `nohup`:
73 | 
74 | ```bash
75 | # Run this as the codebox user
76 | nohup codebox run Workspace/your_project_name -u user1:passwd1,user2:passwd2 &
77 | ```
78 | 
79 | Congratulations! You have now installed and configured the Codebox IDE. If you 
80 | want to learn more about configuring and using the Codebox IDE, be sure to 
81 | check out the articles under the "Codebox IDE" section of the [Codebox Help 
82 | Site](http://help.codebox.io/).
83 | 
84 | 


--------------------------------------------------------------------------------
/en/_posts/2014-10-28-how-to-set-up-an-ipv6-tunnel-on-ubuntu-14.04.markdown:
--------------------------------------------------------------------------------
 1 | ---
 2 | layout: post
 3 | title: "How to set up an IPv6 tunnel on Ubuntu 14.04"
 4 | categories: Instances
 5 | author: DrOfAwesomeness
 6 | lang: en
 7 | ---
 8 | In this guide, I'll show you how to set up IPv6 on RunAbove instances using the free [Tunnelbroker](https://www.tunnelbroker.net) service from Hurricane Electric.
 9 | 
10 | 1. Preparing the tunnel
11 | ===
12 | 
13 | The first thing you'll need to do is create an account on the [Tunnelbroker Site](https://www.tunnelbroker.net/). After you have registered an account, click the "Create Regular Tunnel" button on the left side of the Tunnelbroker portal. Put the IP address of your RunAbove instance in the IPv4 Endpoint field and select a tunnel server from the list (I used the Toronto, ON, CA tunnel server when writing this tutorial.) Next, from your RunAbove control panel, edit your [Security Groups](https://cloud.runabove.com/horizon/project/access_and_security/?tab=access_security_tabs__security_groups_tab) (in OpenStack Horizon under "Access & Security") and allow all TCP traffic from the Tunnel Server IPv4 address (as displayed on the Tunnelbroker "Tunnel Details" page).
14 | 
15 | 2. Connecting to the tunnel
16 | ===
17 | 
18 | Now that your tunnel has been set up, it's time to connect to it. To do so, SSH in to your RunAbove instance, open the /etc/network/interfaces file (`sudo nano /etc/network/interfaces`) and add the following at the end of the file:
19 | 
20 | ```
21 | auto he-ipv6
22 | iface he-ipv6 inet6 v4tunnel
23 |         address <HE Client IPv6 Address>
24 |         netmask 64
25 |         endpoint <HE Server IPv4 Address>
26 |         local <RunAbove Instance IP>
27 |         ttl 255
28 |         gateway <HE Server IPv6 Address>
29 | ```
30 | Be sure to replace `<HE Client IPv6 Address>`, `<HE Server IPv4 Address>`, and `<HE Server IPv6 Address>` with the appropriate information from your Tunnelbroker "Tunnel Details" page and `<RunAbove Instance IP>` with the IPv4 address of your RunAbove instance. Next, to bring the `he-ipv6` interface up, run the following command:
31 | 
32 | ```bash
33 | sudo ifup he-ipv6
34 | ```
35 | 
36 | Your instance now has IPv6 connectivity! Your IPv6 address is the "Client IPv6 Address" shown on the Tunnelbroker "Tunnel Details" page. If you'd like to test your IPv6 connectivity, you can ping Google's IPv6 server with `ping6 ipv6.google.com`. If you don't get any errors, Congrats! If you run into problems or want to learn more about Tunnelbroker, be sure to check out the Tunnelbroker Section of the Hurricane Electric IPv6 [FAQ](https://ipv6.he.net/certification/faq.php).
37 | 


--------------------------------------------------------------------------------
/en/_posts/2014-11-07-private-network-nat.markdown:
--------------------------------------------------------------------------------
 1 | ---
 2 | layout: post
 3 | title: "Configure a private network with NAT"
 4 | categories: instances
 5 | lang: en
 6 | author: NicolasLM
 7 | ---
 8 | 
 9 | A common network layout is to have a gateway handling all the traffic between 
10 | the inside of a network and the outside. This guide will show the simple steps 
11 | on how to reproduce this layout on RunAbove.
12 | 
13 | ![Layout NAT](/kb/images/2014-11-07-private-network-nat/layout.png)
14 | 
15 | Create a new local network
16 | --------------------------
17 | 
18 | Go to OpenStack Horizon and in the `Network Topology` tab click on 
19 | `Create Network`.
20 | 
21 | ### Network
22 | 
23 | Give a name to your network (ie. Local) and set the admin state.
24 | 
25 | ![Network](/kb/images/2014-11-07-private-network-nat/network-step1.png)
26 | 
27 | ### Subnet
28 | 
29 | Create a subnet with a name (ie. Local), select and IP network. Here we use 
30 | `192.168.0.0/24` in IPv4. Finally activate a gateway at `192.168.0.4`.
31 | 
32 | ![Subnet](/kb/images/2014-11-07-private-network-nat/network-step2.png)
33 | 
34 | ### Subnet Detail
35 | 
36 | Enable DHCP and create the network.
37 | 
38 | ![Sub detail](/kb/images/2014-11-07-private-network-nat/network-step3.png)
39 | 
40 | Launch and configure the gateway
41 | --------------------------------
42 | 
43 | Create the gateway as you wish and set the external network as first interface 
44 | and the local one as the second interface.
45 | 
46 | ![NICs](/kb/images/2014-11-07-private-network-nat/network-step4.png)
47 | 
48 | Connect to your instance:
49 | 
50 |     ssh admin@<Public IP of your gateway>
51 | 
52 | Login as root and configure network and NAT routing:
53 | 
54 |     sudo su -
55 |     ifconfig eth1 192.168.0.4/24
56 |     echo 1 > /proc/sys/net/ipv4/ip_forward
57 |     iptables -t nat -A POSTROUTING -o eth0 -j MASQUERADE
58 | 
59 | Launch your internal instances
60 | ------------------------------
61 | 
62 | Create your internal instances, they should have only one private IP address.  
63 | Once you have an address go to your gateway and add a rule to forward the port 
64 | to be able to connect with SSH. For example if your internal instance has the 
65 | address `192.168.0.7` you can create a rule to contact it from the port 2201 of 
66 | your gateway with:
67 | 
68 |     iptables -t nat -A PREROUTING -p tcp --dport 2201 -j DNAT --to-destination 
69 |     192.168.0.7:22
70 | 
71 | Finally open the port 2201 in the security group of your gateway. To do that go 
72 | to `Access & Security` and add a rule to your security group to allow incoming 
73 | TCP traffic to port 2201.
74 | 
75 | You can now connect to your internal instance with:
76 | 
77 |     ssh admin@<Public IP of gateway> -p 2201
78 | 
79 | 


--------------------------------------------------------------------------------
/en/_posts/2014-12-29-security-groups.md:
--------------------------------------------------------------------------------
 1 | ---
 2 | layout: post
 3 | title: "Protect your instances with RunAbove firewall"
 4 | categories: instances
 5 | lang: en
 6 | author: NicolasLM
 7 | ---
 8 | 
 9 | RunAbove encourages you to manage the security of your instances by integrating 
10 | an easy to use firewall in front of all your servers. This guide shows the 
11 | possibilities it offers as well as how to manage it.
12 | 
13 | Security groups
14 | ---------------
15 | 
16 | When you create your RunAbove account we enable for you a security group called 
17 | `default`. All the instances you launch go into this security group by default.
18 | 
19 | You can add an unlimited numbers of rules to this security group. A rule allows 
20 | one kind of traffic to reach or go out of your instance.
21 | 
22 | Default rules
23 | -------------
24 | 
25 | The default security group is populated with four main rules. They allow:
26 | 
27 | * All outgoing traffic
28 | * To access your instance by SSH on port 22
29 | * To access a web server over HTTP on port 80
30 | * To access a web server over HTTPS on port 443
31 | 
32 | All other incoming traffic is denied to protect your instance.
33 | 
34 | Adding a rule
35 | -------------
36 | 
37 | You can easily add a rule to allow another kind of traffic. Go to [OpenStack 
38 | Horizon](https://cloud.runabove.com/horizon/project/access_and_security/), in 
39 | "Access & Security" you will see your security groups. By clicking on "Edit 
40 | rules" you will be able to list the rules that currently apply.
41 | 
42 | Click on "Add Rule" and a form will ask you a few information about the traffic 
43 | you want to allow. Some rules for common services like DNS, RDP or IMAP are 
44 | already shipped.
45 | 
46 | ![Add security rule](/kb/images/2014-12-29-security-groups/add-rule.png)
47 | 
48 | If your service is not in the list select "Custom TCP Rule" and the direction 
49 | "Ingress". Then specify if you only want to open one port or a port range.
50 | 
51 | The "Remote" field has two properties:
52 | 
53 | * CIRD, a network form which the traffic will be allowed. `0.0.0.0/0` means 
54 | everywhere in CIDR notation. You can restrict to one IP with for example 
55 | `83.222.45.67/32`.
56 | * Security group, a security group from which all instances in this group will 
57 | be able to access the service.
58 | 
59 | Going further with security groups
60 | ----------------------------------
61 | 
62 | You can create other security groups for each kind of servers you have. Imagine 
63 | that you have a cluster of web servers and a database server.
64 | 
65 | You can create two security groups (ie. web and database). They will both have 
66 | different rules:
67 | 
68 | * Web, allows traffic on port 80 from everywhere
69 | * Database, allows traffic on port 3306 from the security group web
70 | 
71 | 


--------------------------------------------------------------------------------
/en/_posts/2015-08-10-how-to-get-data-from-runabove-iot.markdown:
--------------------------------------------------------------------------------
 1 | ---
 2 | layout: post
 3 | title: "How to get data from the RunAbove IoT metrics storage"
 4 | categories: iot
 5 | lang: en
 6 | author: babelouest
 7 | ---
 8 | 
 9 | [IoT Labs][6] is an Internet of Things Platform designed to store and retrieve metric data, and automatically compute and process that data.
10 | 
11 | This documentation is about how to get data from the RunAbove IoT metrics storage. It explains how to transfer your data from the service via an https REST API.
12 | 
13 | We assume you have a valid READ token from the application you're working with. Applications and token management is explained in the [How to push data to the RunAbove IoT metrics storage][1]
14 | 
15 | # Get IoT Metrics Data
16 | 
17 | ## Query data from OpenTSDB HTTPS REST API
18 | 
19 | The Runabove Metrics Storage system can be queried using a subset of the OpenTSDB REST API. [OpenTSDB](http://opentsdb.net) is a popular open source time series database which is integrated in many third-party tools such as [collectd](https://collectd.org/wiki/index.php/Plugin:OpenTSDB) or [Grafana](http://grafana.org/)
20 | 
21 | The endpoint to query data via the webservice is at `https://opentsdb.iot.runabove.io/api/query`
22 | 
23 | This endpoint uses the POST method, expecting data in the request body in JSON format. The complete documentation for OpenTSDB queries is available in the official [OpenTSDB Documentation][3]
24 | 
25 | A valid example body has the following form:
26 | 
27 | ```json
28 | {
29 | 	"start":1438956901,
30 | 	"queries":[{
31 | 		"metric":"my.metric",
32 | 		"aggregator":"sum",
33 | 		"tags":{
34 | 		    "boxid": "1F43"
35 | 		}
36 | 	}]
37 | }
38 | ```
39 | 
40 | Please note that RunAbove IoT Metrics Storage does not implement TSUIDs, so a query filter using TSUID will be ignored.
41 | 
42 | The other most common parameters are the following:
43 | 
44 | - start: numeric, start date in Unix Epoch format in seconds (required)
45 | - end: numeric, end date in Unix Epoch format in seconds (optional)
46 | - queries: Array, a list of subqueries to filter data (required)
47 | 
48 | A subquery accepts (but not only) the following parameters:
49 | 
50 | - metric: string, the name of the metric stored (required)
51 | - aggregator: string, the name of the [aggregator function][5] to use (required)
52 | 
53 | The authentication method is a HTTP Basic Auth using a read token: use the token id as the username, and the token key as the password.
54 | 
55 | On success, the body response has the following format:
56 | 
57 | ```json
58 | [{
59 | 	"metric":"my.metric",
60 | 	"tags":{
61 | 		"boxid":"1F43"
62 | 	},
63 | 	"aggregateTags":[],
64 | 	"dps":{
65 | 		"1438956980":1,
66 | 		"1438957000":4,
67 | 		"1438957110":3,
68 | 		"1438957280":1
69 | 	}
70 | }]
71 | ```
72 | 
73 | In this exemple, the main parameters are the following:
74 | 
75 | - metrics: string, the metric name
76 | - tags: object, the common tags for the data,
77 | - dps: object, the data points with the timestamp as key and the numeric value as value.
78 | 
79 | For a complete description, the query parameters are fully described in the official [OpenTSDB documentation][4].
80 | 
81 |   [1]: /kb/en/iot/how-to-push-data-to-runabove-iot.html
82 |   [3]: http://opentsdb.net/docs/build/html/api_http/index.html
83 |   [4]: http://opentsdb.net/docs/build/html/api_http/query/index.html
84 |   [5]: http://opentsdb.net/docs/build/html/api_http/aggregators.html
85 |   [6]: https://runabove.com/iot/
86 | 


--------------------------------------------------------------------------------
/en/_posts/2015-08-24-how-to-sync-runabove-object-storage-containers-to-ovh-public-cloud.markdown:
--------------------------------------------------------------------------------
 1 | ---
 2 | layout: post
 3 | title:  "How to synchronize RunAbove container to OVH Public Cloud?"
 4 | categories: Object-Storage
 5 | author: pilgrimstack
 6 | lang: en
 7 | ---
 8 | 
 9 | Swift provides a very simple way to synchronize different containers even if the source and the destination are not in the same infrastructure. That is our case here with RunAbove Object Storage and OVH Public Cloud.
10 | 
11 | A job runs on the RunAbove Swift server. It will replicate all write transactions in the container on RunAbove to an other on OVH Public Cloud. 
12 | 
13 | # Prerequistes :
14 | 
15 |  * Python installed on your computer ([https://www.python.org/](https://www.python.org/)
16 |  * Openstack swift client ([https://github.com/openstack/python-swiftclient](https://github.com/openstack/python-swiftclient) or curl (Unix)
17 | 
18 | # How it works :
19 | 
20 | The authentication will be done by using a shared key.
21 | 
22 | The source container should have two specials metadata:
23 | 
24 |  * X-Container-Sync-To: the destination of the container on the other infrastructure
25 |  * X-Container-Sync-Key: the shared key between containers
26 | 
27 | The destination container should have one special metadata:
28 | 
29 |  * X-Container-Sync-Key: the shared key between containers
30 | 
31 | # Generate the shared key :
32 | 
33 | ```sharedKey=$(openssl rand -base64 32)
34 | ```
35 | 
36 | # With Python client :
37 | 
38 | Assuming you have sourced your environnement with OVH Public Cloud credentials, you have to add the key to the destiantion container.
39 | 
40 | ```swift post --sync-key "$sharedKey" myContainer
41 | ```
42 | 
43 | Then you have to get the public address of this container.
44 | 
45 | ```destContainer=$(swift --debug stat myContainer 2>&1 | grep 'curl -i.*storage' | awk '{ print $4 }')
46 | ```
47 | 
48 | Now you can tell to the source container which destination it should pushed the data with the shared key.
49 | 
50 | Start by sourcing the RunAbove credentials, then: 
51 | 
52 | ```swift post --sync-key "$sharedKey" --sync-to "$destContainer" myContainer
53 | ```
54 | 
55 | # With cURL :
56 | 
57 | On the destination:
58 | 
59 | ```curl -i https://storage.sbg1.cloud.ovh.net/v1/AUTH_YYYYYYYYY/myContainer
60 |         -X POST -H "X-Container-Sync-Key: $sharedKey" -H "Content-Length: 0" 
61 |         -H "X-Auth-Token: abcd1234" 
62 | ```
63 | 
64 | On the source:
65 | 
66 | ```curl -i https://https://storage.bhs-1.runabove.io/v1/AUTH_XXXXXXX/myContainer 
67 |         -X POST -H "X-Container-Sync-Key: $sharedKey" -H "Content-Length: 0" 
68 |         -H "X-Auth-Token: abcd1234" 
69 |         -H "X-Container-Sync-To: https://storage.sbg1.cloud.ovh.net/v1/AUTH_YYYYYYYYY/myContainer"
70 | ```
71 | 
72 | # Conclusion :
73 | 
74 | This synchronization between two containers is a very good way to migrate data from one infrastructure to another without any service interruption. If you want, you can use it for any others reasons : share objects between openstack users, replicate your data between two geographical and separate infras...
75 | 


--------------------------------------------------------------------------------
/en/_posts/2015-10-13-how-to-use-arm-lab.markdown:
--------------------------------------------------------------------------------
 1 | ---
 2 | layout: post
 3 | title:  "How to subscribe to and use the Arm lab"
 4 | categories: Labs 
 5 | author: xXraphXx
 6 | lang: en
 7 | ---
 8 | 
 9 | Quick tutorial about the way to subscribe to the arm lab and spawn your very first aarch64 virtual machine! List of known issues with arm instances at the end.
10 | 
11 | # Spawn a virtual machine on arm
12 | 
13 | ## Step 1
14 | 
15 | Go to [Runabove](https://www.runabove.com) > Labs > Discover armcloud > Start Now
16 | 
17 | ![Lab](/kb/images/2015-10-13-how-to-use-arm-lab/step1.png)
18 | 
19 | ![Start Lab](/kb/images/2015-10-13-how-to-use-arm-lab/step2.png)
20 |     
21 | ## Step 2
22 | 
23 | Either sign up (create new account) or sign in (use existing account)
24 | 
25 | ![Sign up/in](/kb/images/2015-10-13-how-to-use-arm-lab/step3.png)
26 | 
27 | ## Step 3
28 | 
29 | Important: SSH Keys. Once logged in, you fall back on the classical runabove interface to manage your cloud objects. 
30 | Please make sure that you have registered a public key in region **`HZ-1`** to be used to access your machine once deployed.
31 | 
32 | ![SSH](/kb/images/2015-10-13-how-to-use-arm-lab/step9.png)
33 |     
34 | ## Step 4
35 | 
36 | Create a new instance. Important: take care of choosing the correct region, flavor and image.
37 | 
38 |  * Region: arm instances are only available in region **`HZ-1`**, so make sure you select this region when spawning your server
39 | 
40 |  * Flavor: currently only one flavor available, **`vps-arm-1`**, more to be coming soon
41 | 
42 |  * Image: **`ubuntu-14.04-aarch64`**
43 | 
44 | ![Launch](/kb/images/2015-10-13-how-to-use-arm-lab/step4.png)
45 | 
46 | ![Region](/kb/images/2015-10-13-how-to-use-arm-lab/step5.png)
47 | 
48 | ![Model](/kb/images/2015-10-13-how-to-use-arm-lab/step6.png)
49 | 
50 | ![Flavor](/kb/images/2015-10-13-how-to-use-arm-lab/step7.png)
51 | 
52 | ![Fire](/kb/images/2015-10-13-how-to-use-arm-lab/step8.png)
53 | 
54 | 
55 | # Known issues on arm
56 | 
57 |  * If you were one of the first to subscribe to the lab, you may have entcountered poor disk and network io performances due to the kernel 3.18. The kernel 4.2 will be very soon proposed and is far better in terms of performance, so you may consider respawning a virtual machine from scratch (important: kernel upgrade directly from within the guest won't have the same effect, you won't be rescheduled at the correct place)
58 | 
59 |  * If you are using the 3.18 kernel image, you may entcounter some unstabilities concerning your instances, please forgive us for the disturbance
60 | 
61 |  * Suspend/resume -> currently not working, if your machine falls in ERROR, just shut it down and start it again. 
62 | 
63 |  * Note that as a consequence of the suspend/resume limitation above, live snapshots are not working either. please shutdown your instance before taking any snapshot (actually, under kernel 3.18, the live snapshot will work, but the machine will never resume, so you may as well shut down your instance directly...)
64 | 
65 |  * No vnc console access, but you can still get a serial console access. See this [tutorial](/kb/en/labs/how-to-serial-console-arm-instance.html)
66 | 
67 |  * When subscribing to the lab you are also presented the vps-hdd flavors (vps-hdd-\*) and images, as if you had subscribed to the vps-hdd lab. You can use them as well but this is not arm :). See [here](https://community.runabove.com/kb/en/labs/how-to-use-vps-hdd-lab.html) for more details.
68 | 


--------------------------------------------------------------------------------
/en/_posts/2015-10-13-how-to-use-vps-hdd-lab.markdown:
--------------------------------------------------------------------------------
 1 | ---
 2 | layout: post
 3 | title:  "How to subscribe to and use the VPS-HDD lab"
 4 | categories: Labs 
 5 | author: xXraphXx
 6 | lang: en
 7 | ---
 8 | 
 9 | VPS-HDD: 1 physical disk dedicated to your virtual machine, 1T, 2T and 4T volumes. 
10 | 
11 | # Subscribe
12 | 
13 | Go to [Runabove](https://www.runabove.com) > Labs > Discover Vps-HDD > Start Now
14 | 
15 | ![Lab](/kb/images/2015-10-13-how-to-use-vps-hdd-lab/step1.png)
16 | 
17 | To activate the vps-hdd lab you will have to provide a payment mean
18 | 
19 | ![Activate](/kb/images/2015-10-13-how-to-use-vps-hdd-lab/step2.png)
20 | 
21 | # Spawn your instance(s)
22 | 
23 | Take care of choosing the correct parameters
24 | 
25 |  * Region where VPS-HDD is available: **`HZ-1`**
26 | 
27 |  * Images: Ubuntu 14.04, Debian 7, Fedora 20, CentOS 7
28 | 
29 |  * Flavors: vps-hdd-1000, vps-hdd-2000, vps-hdd-4000
30 | 
31 | ![Region](/kb/images/2015-10-13-how-to-use-vps-hdd-lab/step3.png)
32 | 
33 | # Notes
34 | 
35 |  * When subscribing to the lab, if you go to the openstack dashboard you will also be presented some images related to the armcloud lab (ubuntu-14.04-aarch64), they are not intended (and cannot) be used for vps-hdd. If you still want to use them, subscribe to the arm lab first
36 | 
37 |  * When spawning your vps-hdd you have two disks attached to the virtual machines: one small 10G one containing the rootfs (vda), and the big volume (vdb), with a capacity matching to the flavor you chose (1T, 2T or 4T). By default we have formatted it in ext4 and mounted it on /home. Nothing prevents you from changing this if you want to.
38 | 
39 |  * When you rebuild your instance (nova rebuild, or  through the openstack dahsboard), only the primary disk content is restored. The secondary disk content will be preserved. Only if you terminate/destroy the instance will it be erased
40 | 
41 | ![Disks](/kb/images/2015-10-13-how-to-use-vps-hdd-lab/step4.png)
42 | 
43 | 


--------------------------------------------------------------------------------
/en/_posts/2015-12-10-create-mysql-managed-stack-api.md:
--------------------------------------------------------------------------------
  1 | ---
  2 | layout: post
  3 | title:  "How to create a MySQL Managed Stack using the API"
  4 | categories: ManagedStacks
  5 | author: popawu
  6 | lang: en
  7 | ---
  8 | 
  9 | In this guide you will learn how to create your Managed Stacks MySQL cluster using the API.
 10 | 
 11 | Requirements
 12 | ============
 13 | 
 14 | - applicationKey, consumerKey and signature generated for OVH API access. You will also need to manage timestamps. You can find details on the [first step with the OVH API page.][1]
 15 | 
 16 | For the sake of command lines' brevity you can define this helpful aliases to interact with Managed Stacks API.
 17 | 
 18 | ```bash
 19 | user@desk:~$ MANAGEDSTACKS_LAB=https://api.runabove.com/1.0
 20 | user@desk:~$ alias auth_curl='curl --include -H "X-Ovh-Application:$applicationKey" -H "X-Ovh-Timestamp:$time" -H "X-Ovh-Signature:$signature" -H "X-Ovh-Consumer:$consumerKey" -H "Content-Type: application/json"'
 21 | ```
 22 | 
 23 | Create MySQL Managed Stack
 24 | ===========================
 25 | 
 26 | - CALL
 27 | ```bash
 28 | user@desk:~$ auth_curl -X POST ${MANAGEDSTACKS_LAB}/stackMysql
 29 | ```
 30 | 
 31 | - RETURN
 32 | ```json
 33 | {
 34 |     "msg": "cluster created"
 35 | }
 36 | ```
 37 | 
 38 | Get your cluster's id
 39 | =====================
 40 | 
 41 | - CALL
 42 | ```bash
 43 | user@desk:~$ auth_curl -X GET ${MANAGEDSTACKS_LAB}/stackMysql
 44 | ```
 45 | 
 46 | - RETURN
 47 | ```json
 48 | {
 49 |   "products": [
 50 |     {
 51 |       "id": <clusterId>
 52 |     }
 53 |   ]
 54 | }
 55 | ```
 56 | 
 57 | Get informations about your cluster
 58 | ===================================
 59 | 
 60 | - CALL
 61 | ```bash
 62 | user@desk:~$ auth_curl -X GET ${MANAGEDSTACKS_LAB}/stackMysql/<clusterId>
 63 | ```
 64 | 
 65 | - RETURN
 66 | ```json
 67 | {
 68 |   "active": <true|false>,
 69 |   "nodes": [
 70 |     {
 71 |       "addr": "<ipAddressNode1>",
 72 |       "product_id": <productId>
 73 |     },
 74 |     {
 75 |       "addr": "<ipAddressNode2>",
 76 |       "product_id": <productId>
 77 |     }
 78 |   ],
 79 |   "product_id": <productId>
 80 | }
 81 | ```
 82 | 
 83 | Get monitoring status information about your cluster
 84 | ====================================================
 85 | 
 86 | 
 87 | - CALL
 88 | ```bash
 89 | user@desk:~$ auth_curl -X GET ${MANAGEDSTACKS_LAB}/stackMysql/<clusterId>/status
 90 | ```
 91 | 
 92 | - RETURN
 93 | Json object, list of probes for each node. The object key is the probe name, object value is the result.
 94 | 
 95 | Delete your cluster
 96 | ===================
 97 | 
 98 | - CALL
 99 | ```bash
100 | user@desk:~$ auth_curl -X DELETE ${MANAGEDSTACKS_LAB}/stackMysql/<clusterId>
101 | ```
102 | 
103 | - RETURN
104 | ```json
105 | {
106 |   "msg": "cluster deleted"
107 | }
108 | ```
109 | 
110 | Go further
111 | ==========
112 | 
113 | You may have a look at:
114 | 
115 | - Guide: [Create MySQL Managed Stack from RunAbove manager][2]
116 | 
117 | [1]: https://api.ovh.com/g934.first_step_with_api
118 | [2]: create-mysql-managed-stack.html
119 | 


--------------------------------------------------------------------------------
/en/_posts/2015-12-10-create-mysql-managed-stack.md:
--------------------------------------------------------------------------------
 1 | ---
 2 | layout: post
 3 | title:  "How to create a MySQL Managed Stack"
 4 | categories: ManagedStacks
 5 | author: popawu
 6 | lang: en
 7 | ---
 8 | 
 9 | Deploy your database stack, we take care of it !
10 | 
11 | In this guide you will learn how to subscribe to the Managed Stacks lab and create your MySQL cluster.
12 | 
13 | Now available with your cluster :
14 | 
15 | - MySQL High availability : 2 MySQL nodes with SSL master/master replication
16 | - Real-time resources visualization : Monitoring probes to check MySQL status, server load and disk space on each node
17 | - Managed stack : 24/7 hardware/software monitoring and system security management
18 | 
19 | New features will be added soon and this guide will be updated accordingly.
20 | Enjoy !
21 | 
22 | 
23 | Requirements
24 | ============
25 | 
26 |  * MySQL client ([http://dev.mysql.com/doc/refman/5.7/en/programs-client.html](http://dev.mysql.com/doc/refman/5.7/en/programs-client.html)
27 | 
28 | Activate Managed Stacks lab
29 | ===========================
30 | 
31 | Go to [Runabove](https://www.runabove.com) > Labs > Discover Managed Stacks > Start Now
32 | 
33 | ![Start Lab](/kb/images/2015-12-10-create-mysql-managed-stack/start.png)
34 | 
35 | Either sign up (create new account) or sign in (use existing account)
36 | 
37 | ![Sign up](/kb/images/2015-12-10-create-mysql-managed-stack/signup.png)
38 | 
39 | To activate Managed Stacks Lab, click on 'More labs...' and 'Activate'
40 | 
41 | ![Activate](/kb/images/2015-12-10-create-mysql-managed-stack/activate.png)
42 | 
43 | Create MySQL Managed Stack
44 | ============================
45 | 
46 | To create a new stack, click on 'Managed stacks' in the left menu, and then on '+ New stack'.
47 | 
48 | ![Managed Stacks](/kb/images/2015-12-10-create-mysql-managed-stack/menu_managed.png)
49 | 
50 | ![New Stack](/kb/images/2015-12-10-create-mysql-managed-stack/new_stack.png)
51 | 
52 | You will receive an email confirming the creation of your new stack.
53 | 
54 | Start using your Create MySQL Managed Stack
55 | ===========================================
56 | 
57 | Wait for your to stack to be in active status. The stack delivery last about 10 minutes.
58 | 
59 | ![status_active](/kb/images/2015-12-10-create-mysql-managed-stack/status_active.png)
60 | 
61 | Once your stack is active, you will receive a second email containing all information about it :
62 | * IP/Hostname of the first node of your cluster
63 | * IP/Hostname of the second node of your cluster
64 | * root and user account of your cluster
65 | 
66 | You can test your access to the nodes with this command :
67 | ```bash
68 | user@desk:~$ mysql -u{username} -p{password} -h{node IP or hostname}
69 | ```
70 | 
71 | You can get the details of your stack by clicking on the application name :
72 | 
73 | ![stack_details](/kb/images/2015-12-10-create-mysql-managed-stack/stack_details.png)
74 | 
75 | You will see details of your cluster and 3 monitoring probes for each node.
76 | 
77 | ![cluster_status](/kb/images/2015-12-10-create-mysql-managed-stack/cluster_status.png)
78 | 
79 | Delete your Managed Stacks MySQL cluster
80 | ========================================
81 | 
82 | Click on 'Managed stacks' in the left menu, and then on the garbage in the action column :
83 | 
84 | ![delete_stack1](/kb/images/2015-12-10-create-mysql-managed-stack/delete_stack1.png)
85 | 
86 | Confirm your action :
87 | 
88 | ![delete_stack2](/kb/images/2015-12-10-create-mysql-managed-stack/delete_stack2.png)
89 | 


--------------------------------------------------------------------------------
/en/_posts/2016-02-24-how-to-log-your-linux.md:
--------------------------------------------------------------------------------
 1 | ---
 2 | layout: redirected
 3 | title:  "How to log your Linux with syslog-ng 3.0+"
 4 | categories: Logs
 5 | author: baaastijn
 6 | lang: en
 7 | sitemap: false
 8 | redirect_to:  https://docs.ovh.com/gb/en/mobile-hosting/logs-data-platform/how-to-log-your-linux/
 9 | ---
10 | 
11 | You have a server, a raspberry pi, a cloud instance or something else
12 | running on `Linux` and you want to follow your Logs, the easy way ?
13 | You have never installed a log collector and you're new with Graylog ?
14 | 
15 | 
16 | This tutorial is for you then !
17 | 
18 | 
19 | In this tutorial you will learn from A to Z how to send Logs from your linux instance to PaaS Logs. 
20 | Don't be afraid, it will be easier than you think. 
21 | 


--------------------------------------------------------------------------------
/en/_posts/2016-02-25-android-nxlog.md:
--------------------------------------------------------------------------------
 1 | ---
 2 | layout: redirected
 3 | title:  "Sending Android 4.4 Logs with NXLog to PaaS Logs"
 4 | categories: Logs
 5 | author: Babacar Diassé
 6 | lang: en
 7 | sitemap: false
 8 | redirect_to:  https://docs.ovh.com/gb/en/mobile-hosting/logs-data-platform/android-nxlog/
 9 | ---
10 | 
11 | If you have a device running Android 4.4 Kitkat or less, like a smart TV, or a set-top box or simply a phone that hasn't been updated to Lollipop and that you were always wondering what it was doing all day, this tutorial can give you the answer. [NXlog](https://nxlog.co) has developped an Android app that will allows you to send the logs of your phones to PaaS Logs. Its configuration is fairly simple and you will able to witness your logs in PaaS logs in minutes. So let's get started !
12 | 
13 | 
14 | In order to complete this tutorial you will have to have created and activated your account on PaaS Logs and be able to send your logs to a stream.
15 |  
16 |   - [Activate the PaaS Logs lab and created an account.](/kb/en/logs/quick-start.html#account)
17 |   - [Create one Stream and get its token.](/kb/en/logs/quick-start.html#streams)
18 | 
19 | 


--------------------------------------------------------------------------------
/en/_posts/2016-02-25-apache-logs.md:
--------------------------------------------------------------------------------
 1 | ---
 2 | layout: redirected
 3 | title:  "Sending Apache Access Logs in PaaS Logs"
 4 | categories: Logs
 5 | author: Babacar Diassé
 6 | lang: en
 7 | sitemap: false
 8 | redirect_to: https://docs.ovh.com/gb/en/mobile-hosting/logs-data-platform/apache-logs/
 9 | ---
10 | 
11 | <div class="notice--warning" style="border: 1px #CE6D00 solid;padding: 10px;">
12 |   <h4 style="margin-top:0;">DISCLAIMER</h4>
13 |   <p>The following procedure have the advantage to be setup very quickly but is NOT recommended at all in production as it can block the Apache process in case of heavy traffic.</p>
14 |   <p>
15 |         In production, please use a non blocking solution as this one: <a href="https://community.runabove.com/kb/en/logs/filebeat-logs.html">Shipping logs to PaaS Logs with Filebeat</a>
16 |   </p>
17 | </div>
18 | 
19 | Apache access logs are very valuable. They show the activity of your visitors, the page delivery time, the code results, the user agent that accessed your websites.
20 | The default log line looks like this
21 | 
22 | ```
23 | 51.255.160.250 - - [23/Jan/2016:19:33:03 +0100] "GET / HTTP/1.1" 200 14211 "-" "Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.7.12) Gecko/20050915 Firefox/1.0.7"
24 | ```
25 | 
26 | This is already giving a lot of information but it can be troublesome to extract really useful data from plain text logs.
27 | You maybe know that there is a already lot of ways to export your Apache logs: logstash, beats, graylog-collector, syslog-ng, rsyslog, gelf apache module. But as we have still a lot to explore in the PaaS Logs, let's start with something simple :-).
28 | This tutorial will present you the less intrusive way to log to PaaS Logs : ask Apache to pipe log entries directly to PaaS Logs.
29 | 


--------------------------------------------------------------------------------
/en/_posts/2016-02-25-filebeat-logs.md:
--------------------------------------------------------------------------------
 1 | ---
 2 | layout: redirected
 3 | title:  "Shipping logs to PaaS Logs with Filebeat"
 4 | categories: Logs
 5 | author: Pierre de Paepe
 6 | lang: en
 7 | sitemap: false
 8 | redirect_to: https://docs.ovh.com/gb/en/mobile-hosting/logs-data-platform/filebeat-logs/
 9 | ---
10 | 
11 | Filebeat is an [open source](https://github.com/elastic/beats/tree/master/filebeat) file harvester, mostly used to fetch logs files and feed them into logstash. Together with Logstash, Filebeat is a really powerful tool that allows you to parse and send your logs to PaaS logs in a elegant and non intrusive way (except installing filebeat of course ;-). 
12 | 
13 | This guide will describe how to ask OVH to host your own dedicated Logstash on PaaS Logs and how to setup Filebeat on your system to forward your logs to it. It will also present you with some configuration setup you can use on Logstash to further structure your logs. Note that in order to complete this tutorial, you should have at least: 
14 | 
15 |   - [Activated the PaaS Logs lab and created an account.](/kb/en/logs/quick-start.html#account)
16 |   - [created at least one Stream and get its token.](/kb/en/logs/quick-start.html#streams)
17 | 
18 | Once you have done theses two steps, you can dig into this one. Be prepared. 
19 | 
20 | 


--------------------------------------------------------------------------------
/en/_posts/2016-02-25-windows-nxlog.md:
--------------------------------------------------------------------------------
 1 | ---
 2 | layout: redirected
 3 | title:  "Sending Windows Logs with NXLog to PaaS Logs in 15 minutes or less"
 4 | categories: Logs
 5 | author: Babacar Diassé
 6 | lang: en
 7 | sitemap: false
 8 | redirect_to: https://docs.ovh.com/gb/en/mobile-hosting/logs-data-platform/windows-nxlog/
 9 | ---
10 | 
11 | 
12 | At OVH, we love Microsoft products too. So it is important for us to provide you a way to send your Windows Logs to PaaS Logs. All you need is 15 minutes and one software : [NXLog](http://nxlog.co). NXLog is one of the leader of the log management tools. Its configuration is fairly simple and can get you started in a few minutes. 
13 | 
14 | 
15 | For this tutorial you will need to have completed the following steps : 
16 | 
17 |   - [Activate the PaaS Logs lab and create an account.](/kb/en/logs/quick-start.html#account)
18 |   - [To create at least one Stream and get its token.](/kb/en/logs/quick-start.html#streams)
19 | 
20 | 
21 | 


--------------------------------------------------------------------------------
/en/_posts/2016-02-26-bonfire.md:
--------------------------------------------------------------------------------
 1 | ---
 2 | layout: redirected
 3 | title:  "How to query logs from command line"
 4 | categories: Logs
 5 | author: Pierre De Paepe
 6 | lang: en
 7 | sitemap: false
 8 | redirect_to: https://docs.ovh.com/gb/en/mobile-hosting/logs-data-platform/bonfire/
 9 | ---
10 | 
11 | Bonfire is a open source command line interface to query Graylog searches via the REST API. It tries to emulate the feeling of using tail on a local file and add other valuable options.
12 | 
13 | # Requirements
14 | 
15 |   - Python
16 |   - Pip
17 | 
18 | # Install
19 |  
20 | ```console
21 | $ git clone https://github.com/blue-yonder/bonfire.git
22 | $ cd bonfire
23 | $ pip install --user .
24 | ```
25 | 
26 | 


--------------------------------------------------------------------------------
/en/_posts/2016-02-27-djehouty.md:
--------------------------------------------------------------------------------
 1 | ---
 2 | layout: redirected
 3 | title:  "Push logs with python"
 4 | categories: Logs
 5 | author: cdumay
 6 | lang: en
 7 | sitemap: false
 8 | redirect_to: https://docs.ovh.com/gb/en/mobile-hosting/logs-data-platform/djehouty/
 9 | ---
10 | 
11 | Djehouty is intended to be a set of logging formatters and handlers to easily send log entries into PaaS Logs.
12 | 
13 | This package includes:
14 | 
15 | - for [GELF](http://docs.graylog.org/en/latest/pages/gelf.html):
16 |   - a TCP/TLS handler to send log entries over TCP with TLS support.
17 |   - a formatter to convert logging record into GELF(1.1).
18 | 
19 | - for [LTSV](http://ltsv.org/):
20 |   - a TCP/TLS handler to send log entries over TCP with TLS support.
21 |   - a formatter to convert logging record into LTSV.
22 | 
23 | 


--------------------------------------------------------------------------------
/en/_posts/2016-02-27-logstash-input.md:
--------------------------------------------------------------------------------
 1 | ---
 2 | layout: redirected
 3 | title:  "All you have to know about the Logstash Input on PaaS Logs !"
 4 | categories: Logs
 5 | author: Babacar Diassé
 6 | lang: en
 7 | sitemap: false
 8 | redirect_to: https://docs.ovh.com/gb/en/mobile-hosting/logs-data-platform/logstash-input/
 9 | ---
10 | 
11 | 
12 | "All you have to know about the Logstash Input on PaaS Logs" is your main source of information about deploying a Logstash input on PaaS Logs. Logstash is a software developed by Elastic and allows you to send messages from different inputs to different type of output using different codec while processing them and transforming them in the process.
13 | You can learn a lot more about it on [the official website](https://www.elastic.co/products/logstash). We believe that it is a powerful tool that you would love to use with PaaS Logs. Yes, on PaaS Logs you can deploy your personal Logstash with your own configuration. That will allow you for example to send your data from many sources to one and only Logstash instead of configuring one on each of your host. You will find which plugins are supported, which ones are not and how to spawn a Logstash input on PaaS Logs.
14 | 
15 | This is a rather long document but if you are already familiar with Logstash you can jump to the parts you're interested in :  
16 | 
17 |  - [What is Logstash](#logstash_101)
18 |  - [How do I configure Logstash on PaaS Logs](#paas_config)
19 |  - [What is special about our hosted Logstash ?](#additional)  
20 | 
21 | This is "All you have to know about the Logstash Input on PaaS Logs" !
22 | 


--------------------------------------------------------------------------------
/en/_posts/2016-02-27-tokens-paas-logs.md:
--------------------------------------------------------------------------------
 1 | ---
 2 | layout: redirected
 3 | title:  "Using tokens to query PaaS Logs"
 4 | categories: Logs
 5 | author: Babacar Diassé
 6 | lang: en
 7 | sitemap: false
 8 | redirect_to: https://docs.ovh.com/gb/en/mobile-hosting/logs-data-platform/tokens-logs-data-platform/ 
 9 | ---
10 | 
11 | 
12 | With PaaS Logs, there are 3 ways to query your logs.
13 |  
14 |  - The [Graylog Web Interface](https://graylog.laas.runabove.com)
15 |  - The [Graylog API](https://laas.runabove.com:12900/api-browser#!/Search/Relative)
16 |  - The [Elasticsearch API](https://www.elastic.co/guide/en/elasticsearch/reference/current/search.html) located at https://laas.runabove.com:9200 against your [alias](/kb/en/logs/using-kibana-with-laas.html#alias). 
17 | 
18 | 
19 | So you can pop up a [Kibana](/kb/en/logs/using-kibana-with-laas.html) or a [Grafana](/kb/en/logs/using-grafana-with-laas.html) or even [a terminal Dashboard for Graylog](https://github.com/Graylog2/cli-dashboard). All these accesses are secured by your username and password. But what if you don't want to put your PaaS Logs credentials everywhere? You can just use tokens to access all these endpoints and revoke them anytime you want. This tutorial is here to tell you how.
20 | 
21 | 


--------------------------------------------------------------------------------
/en/_posts/2016-02-28-field-naming-conventions.md:
--------------------------------------------------------------------------------
 1 | ---
 2 | layout: redirected
 3 | title:  "Field Naming convention"
 4 | categories: Logs
 5 | author: Babacar Diassé
 6 | lang: en
 7 | sitemap: false
 8 | redirect_to: https://docs.ovh.com/gb/en/mobile-hosting/logs-data-platform/field-naming-conventions/
 9 | ---
10 | 
11 | Now that you can send logs, you are maybe wondering how to tell PaaS Logs what kind of data you send. It can be date, or number or boolean or just plain string. At OVH, we love to create fancy dashboards with all these kind of stuff. If you want to be sure that your logs will be properly parsed, this document is made for you !
12 | 
13 | 


--------------------------------------------------------------------------------
/en/_posts/2016-02-28-using-grafana-with-laas.md:
--------------------------------------------------------------------------------
 1 | ---
 2 | layout: redirected
 3 | title:  "Using Grafana with PaaS Logs"
 4 | categories: Logs
 5 | author: Pierre De Paepe
 6 | lang: en
 7 | sitemap: false
 8 | redirect_to: https://docs.ovh.com/gb/en/mobile-hosting/logs-data-platform/using-grafana-with-logs/
 9 | ---
10 | 
11 | Grafana provides a powerful and elegant way to create, explore, and share dashboards and data with your team and the world.
12 | Since release 2.5, Grafana is able to communicate with Elasticsearch and so allow you to mix data from PaaS Logs and other data sources like IoT at the same place.
13 | 
14 | This is what you need to know to get you started :  
15 | 
16 |  - you already sending logs on a stream you own [see the quick start tutorial](/kb/en/logs/quick-start.html)
17 |  - your web server can reach https://laas.runabove.com:9200. 
18 | 
19 | After some training you will be able to do this kind of Dashboard : 
20 | ![Grafana Dashboard](/kb/images/2016-02-28-using-grafana-with-laas/grafana.png)
21 | 
22 | 


--------------------------------------------------------------------------------
/en/_posts/2016-02-28-using-timelion-with-laas.md:
--------------------------------------------------------------------------------
 1 | ---
 2 | layout: redirected
 3 | title:  "Using Timelion with PaaS Logs"
 4 | categories: Logs
 5 | author: Babacar Diassé
 6 | lang: en
 7 | sitemap: false
 8 | redirect_to: https://docs.ovh.com/gb/en/mobile-hosting/logs-data-platform/using-timelion-with-logs/
 9 | ---
10 | 
11 | Timelion is a Kibana plugin wich allows you to query multiple datasources from a single Kibana instance a bit like Grafana. This tool is very powerful to analyze metric contained in logs (or simply the logs count) sent to Elasticsearch (so PaaS Logs here). What you can do include but is not limited to :
12 | 
13 |  - Compute an average over a period of time, compute a moving average over a period of time
14 |  - Compute the derivative of a metric or the results of a specific query to quickly see the variations. 
15 |  - Doing arithmetic operation between your metric (division, sum, cumulative sum, multiply, percentage...)
16 |  - Grabbing series from other sources to mix your datas with It ([Quandl](https://www.quandl.com), [World Bank Indicators](http://data.worldbank.org/), [Graphite](http://graphite.readthedocs.io/en/latest/)). 
17 | 
18 | All the informations about this wonderful plugin can be found here :
19 | 
20 | 


--------------------------------------------------------------------------------
/en/_posts/2016-02-29-using-kibana-with-laas.md:
--------------------------------------------------------------------------------
 1 | ---
 2 | layout: redirected
 3 | title:  "Using Kibana with PaaS Logs"
 4 | categories: Logs
 5 | author: Babacar Diassé
 6 | lang: en
 7 | sitemap: false
 8 | redirect_to: https://docs.ovh.com/gb/en/mobile-hosting/logs-data-platform/using-kibana-with-logs/
 9 | ---
10 | 
11 | You want to unleash the full power of Kibana and be able to craft some beautiful Dashboards from your logs. Rest assured, you have come to the right place. 
12 | Kibana is a powerful weapon, the knowledge you are about to read needs you to have reached a certain level (but way below 9000) in the understanding of PaaS Logs. This is what you need to know to get you started :  
13 | 
14 |  - you are already sending logs on a stream you own [see the quick start tutorial](/kb/en/logs/quick-start.html)
15 |  - your web server can reach https://laas.runabove.com:9200. 
16 | 
17 | After some training you will be able to do this kind of Dashboard : 
18 | ![Kibana Dashboard](/kb/images/2016-02-29-using-kibana-with-laas/kibana.png)
19 | 
20 | 


--------------------------------------------------------------------------------
/en/_posts/2016-03-08-quick-start.md:
--------------------------------------------------------------------------------
 1 | ---
 2 | layout: redirected
 3 | title:  "Quick start"
 4 | categories: Logs
 5 | author: Babacar Diassé
 6 | lang: en
 7 | sitemap: false
 8 | redirect_to: https://docs.ovh.com/gb/en/mobile-hosting/logs-data-platform/quick-start/
 9 | ---
10 | 
11 | Welcome to the quick start tutorial of the PaaS Logs. This Quick start guide will help you to understand the core concepts behind the PaaS Logs and how to send your first logs to the engine. 
12 | 
13 | 
14 | #1 Welcome to PaaS Logs. <a name="account">&nbsp;</a>
15 | 
16 | If you have already setup a lab, this procedure should be easy for you. 
17 | 
18 |  - Log into runabove.com and in the console, activate the Labs by clicking on `more Labs...` and then click on the `PaaS Logs` button.
19 |  - Once Activated a new entry will appear in the navigation sidebar, click on the `PaaS Logs` button there to jump to the main interface.
20 |  - The main interface of PaaS Logs will then appear. 
21 |  - On this page, you have only one action available: `Create user`. You will then have a username in the following form: ra-logs-XXXXX and the password associated. `NOTE THEM CAREFULLY`, theses credentials will be the one you will have to use on `Graylog` and with Kibana later (you will know soon enough how to do it). 
22 | 
23 | 


--------------------------------------------------------------------------------
/en/_posts/2016-04-23-marathon-health-checks.md:
--------------------------------------------------------------------------------
 1 | ---
 2 | layout: post
 3 | title:  "Health checks with Marathon"
 4 | categories: Docker
 5 | author: devatoria
 6 | lang: en
 7 | ---
 8 | 
 9 | Health checks are useful to ensure that your containers are running; and even better, are behaving as expected. If your container is found to be unhealthy, it will be automatically redeployed. You can add multiple health checks per application. Marathon supports both high level HTTP and lower level TCP health checks.
10 | 
11 | HTTP checks allow for better, higher level checks on a specific URL like `http://localhost:port/my/health/path`. It automatically ignores informational status codes in the range 100 to 199.
12 | 
13 | # Configure a health check for a nginx application
14 | 
15 | In one of the [previous tutorials](/kb/en/docker/quick-start-with-marathon.html), we deployed and ran a simple nginx container on Marathon. Let's now configure some HTTP health check for this application.
16 | 
17 | ![Main interface](/kb/images/2016-04-20-marathon-health-checks/health_check.png)
18 | 
19 | - **Grace Period**: health check failures are ignored within this number of seconds or until the task becomes healthy for the first time *(useful if you have a task with a long startup time, to avoid having the  health check failing because of this)*.
20 | - **Interval**: number of seconds to wait between each health check
21 | - **Timeout**: number of seconds after which a health check is considered a failure regardless of the response.
22 | 
23 | ##Configure the port to check
24 | 
25 | There are two ways to configure the port to check: by port *index* or by port *number*. By default, the port is passed by index: 0 is the first port you passed in the port mapping configuration, 1 is the second one, etc. You can also specify a port by simply choosing the **port number** type.
26 | 


--------------------------------------------------------------------------------
/en/_posts/2016-04-24-marathon-container-logs.md:
--------------------------------------------------------------------------------
 1 | ---
 2 | layout: post
 3 | title:  "Marathon containers logs in Logs Data Plateform"
 4 | categories: Docker
 5 | author: devatoria
 6 | lang: en
 7 | ---
 8 | 
 9 | It may be useful to send your application logs to the [Logs Data Platform](https://www.ovh.com/fr/data-platforms/logs/). Indeed, if your containers stop, or if you want to be able to debug something, you will be happy to have access to your application logs.
10 | 
11 | #Setup Log Data Plateform
12 | First you need an account on *Logs Data Platform*, you can find all information you need to begin on the [Logs Data Platform quick start guide](https://docs.ovh.com/gb/en/mobile-hosting/logs-data-platform/quick-start/).
13 | 
14 | To be able to push logs into the *Logs Data Platform*, you have to get the token, the address and port of your *Logs Data Plateform* stream for Gelf format from the sunrise manager.
15 | 
16 | you can retrieve the token from the *Logs Data Platform* manager > graylog stream page. There is a "Copy the token" button you can click on :
17 | ![graylog stream list](/kb/images/2016-04-21-marathon-logs/token.png)
18 | 
19 | The address and port can be found on *Logs Data Platform* manager > about page :
20 | ![about page](/kb/images/2016-04-21-marathon-logs/about.png)
21 | 
22 | Be sure to get the port for **Gelf** in **TCP/TLS**, usually it's *12202*.
23 | 
24 | You will find more information on the [Logs Data Platform quick start guide](https://docs.ovh.com/gb/en/mobile-hosting/logs-data-platform/quick-start/).
25 | 
26 | #Inject Logs Data Plateform infos into my container
27 | Once you have your token, adress and port, you must inject them into your application containers using the following labels when creating or editing your app.
28 | 
29 | ```
30 | +------------------------------+-------------------+
31 | | Label name                   | Label value       |
32 | +==============================+===================+
33 | | CONTAINERS_LOG_LOGS_SINKADDR | gra1.logs.ovh.com |
34 | +------------------------------+-------------------+
35 | | CONTAINERS_LOG_LOGS_SINKPORT | 12202             |
36 | +------------------------------+-------------------+
37 | | CONTAINERS_LOG_LOGS_TOKEN    | "your token"      |
38 | +------------------------------+-------------------+
39 | ```
40 | 
41 | It will result in something like this in marathon:
42 | 
43 | ![marathon labels](/kb/images/2016-04-21-marathon-logs/labels.png)
44 | 
45 | You should know see your logs in Graylog. To access Graylog please refer to [Logs Data Platform quick start guide](https://docs.ovh.com/gb/en/mobile-hosting/logs-data-platform/quick-start/).
46 | 


--------------------------------------------------------------------------------
/en/_posts/2016-04-25-marathon-container-metrics.md:
--------------------------------------------------------------------------------
 1 | ---
 2 | layout: post
 3 | title:  "Marathon containers metrics in DBaaS Time Series"
 4 | categories: Docker
 5 | author: devatoria
 6 | lang: en
 7 | ---
 8 | 
 9 | We integrated the Docker PaaS with the [DBaaS Time Series](https://www.ovh.com/fr/dbaas/timeseries/), to allow you to graph your application metrics about your containers in a Grafana dashboard. We automatically send metrics for:
10 | 
11 | - CPU usage
12 | - memory usage
13 | - network I/O
14 | - disk I/O
15 | - out of memory kill count (coming soon!)
16 | 
17 | #Configure your token
18 | 
19 | From the RunAbove manager, join the DBaaS Time Series lab and generate a new credentials pair (read/write). Next, inject the write credentials into your applications using `USER_TIMESERIES_ID` and `USER_TIMESERIES_KEY` labels.
20 | 
21 | ![Main interface](/kb/images/2016-04-21-marathon-metrics/metrics.png)
22 | 
23 | Metrics are aggregated, averaged and pushed every minute.
24 | 
25 | #Analyse my data
26 | ##Create graphs
27 | 
28 | Once your applications metrics are sent to the DBaaS Time Series, you can create some graphs to easily watch how your applications behave, and adapt your stack according to your needs. Available metrics for graphs are:
29 | 
30 | - cpu
31 | - memory.usage
32 | - memory.limit
33 | - network.rx
34 | - network.tx
35 | - blkio.input
36 | - blkio.output
37 | 
38 | ![Main interface](/kb/images/2016-04-21-marathon-metrics/metrics_cpu.png)
39 | 
40 | ###Filtering using tags
41 | 
42 | On each metrics, you can filter on the following tags:
43 | 
44 | - frameworkID: your marathon ID (useful if you have multiple stack logging metrics with the same credentials)
45 | - appID: your application ID (useful if you want to graph multiple applications instead of the full stack)
46 | - taskID: your task ID (identifying a single container)
47 | 
48 | ###CPU data
49 | 
50 | The CPU data are not dependent of the host capacity, but on the limit you are setting in your application. For example, if you create an application with 2 cpus, and if it consumes only one, your CPU usage will be 50%
51 | 
52 | Be careful though, if you create an application with a cpu limit less than one, let's say 0.5, the application could be able to consume one cpu if needed resources are available. Your CPU usage will be 200%.
53 | 
54 | To interpret your data in Grafana, you have multiple ways. We have two interesting use cases:
55 | 
56 | - you have a few apps, or a graph per app: you should filter your CPU usage metrics using the flag `taskID: *` and a `sum aggregate`
57 | - you have a lot of apps to be displayed in a single graph: you should filter your CPU usage metrics using the flag `appID: *` and an `average aggregate`
58 | 
59 | ###Memory data
60 | 
61 | As for the CPU data, the usage and limit increase depending on your instances count. We recommend to use task ID tags to make the data more readable.
62 | 
63 | ###Networking and disk data
64 | 
65 | These data are cumulative. We recommend to use rate graphs for these values, so you will be able to see usage variation. Be careful, you can sometime have **negative values**. This usually happens on a scale down because of the rate graph: collected data are cumulative, and when a container is deleted, they are removed from the sum. So, the rate is interpreting this as a negative value.
66 | 


--------------------------------------------------------------------------------
/en/_posts/2016-05-03-how-to-use-deskaas-lab.md:
--------------------------------------------------------------------------------
 1 | ---
 2 | layout: post
 3 | title:  "How to subscribe to and use the DeskaaS lab"
 4 | categories: vdi
 5 | author: lrivallain
 6 | lang: en
 7 | ---
 8 | 
 9 | ## Joining the lab
10 | 
11 | Beforehand, make sure to have an OVH.com account. If you don't, you may create one from [ovh.com](https://www.ovh.com/manager/web/login/) and select "Create Account"
12 | 
13 | ### From RunAbove website
14 | 
15 | To order : Visit [https://www.runabove.com/deskaas.xml](https://www.runabove.com/deskaas.xml) and clic on "Start Now !"
16 | 
17 | You'll be redirected to the order wizard and will receive a mail with deskaas login and url.
18 | 
19 | ### From OVH.com customer interface
20 | 
21 | Log-in on customer interface. Deskaas product is available in the "sunrise" part of customer interface.
22 | 
23 | Clic on the "**+**" link at the right of "Desktop as a service" ):
24 | 
25 | ![Order](/kb/images/2016-05-03-how-to-use-deskaas-lab/orderfrommanager.png)
26 | 
27 | You'll be redirected to the order wizard and will receive a mail with deskaas login and url.
28 | 
29 | ## Available offers
30 | 
31 | Currently, only one offer is available :
32 | 
33 | *   1 core + 2GB RAM + 10GB Storage + Windows OS
34 | 
35 | ![Lab](/kb/images/2016-05-03-how-to-use-deskaas-lab/offers.png)
36 | 
37 | We are planned to quickly add more models with more storage, RAM or CPU cores. Stay tuned!
38 | 
39 | 
40 | ## Quickstart
41 | 
42 | ### Web client access
43 | 
44 | The delivery mail contains an URL of the form of https://*.deskaas.com to join the web client:
45 | 
46 | ![web_client_welcome](/kb/images/2016-05-03-how-to-use-deskaas-lab/web_client_welcome.png)
47 | 
48 | Use the mail credentials to log-in:
49 | 
50 | ![web_client_login](/kb/images/2016-05-03-how-to-use-deskaas-lab/web_client_login.png)
51 | 
52 | Then it's possible to open the virtual desktop:
53 | 
54 | ![web_client_launchitems](/kb/images/2016-05-03-how-to-use-deskaas-lab/web_client_launchitems.png)
55 | 
56 | Virtual desktop can now be used directly through the web browser:
57 | 
58 | ![web_client_desktop](/kb/images/2016-05-03-how-to-use-deskaas-lab/web_client_desktop.png)
59 | 
60 | A settings menu is available on the left side of the desk :
61 | 
62 | ![web_client_menu](/kb/images/2016-05-03-how-to-use-deskaas-lab/web_client_menu.png)
63 | 
64 | 
65 | ### Software client
66 | 
67 | A software client is available on most OS to access to the virtual desktop : [vmware_horizon_clients](https://my.vmware.com/en/web/vmware/info/slug/desktop_end_user_computing/vmware_horizon_clients/4_0)
68 | 
69 | Once the client is install and launched, you can create a shortcut for the server:
70 | 
71 | ![soft_new-server](/kb/images/2016-05-03-how-to-use-deskaas-lab/soft_new-server.png)
72 | 
73 | Add the <a>https://*.deskaas.com</a> URI from the mail and validate:
74 | 
75 | ![soft_lists-servers](/kb/images/2016-05-03-how-to-use-deskaas-lab/soft_lists-servers.png)
76 | 
77 | Click on server to log-in:
78 | 
79 | ![soft_authentication](/kb/images/2016-05-03-how-to-use-deskaas-lab/soft_authentication.png)
80 | 
81 | Then, the list of available desktop is displayed :
82 | 
83 | ![soft_list-desktops](/kb/images/2016-05-03-how-to-use-deskaas-lab/soft_list-desktops.png)
84 | 
85 | And virtual desktop is ready to used:
86 | 
87 | ![soft_logged-in](/kb/images/2016-05-03-how-to-use-deskaas-lab/soft_logged-in.png)
88 | 
89 | ## Useful links
90 | * [Discover Desktop as a service lab](https://www.runabove.com/deskaas.xml)
91 | * Subscribe to the mailing list: [deskaas-subscribe@ml.ovh.net](mailto:deskaas-subscribe@ml.ovh.net)
92 | 


--------------------------------------------------------------------------------
/en/_posts/2016-07-11-service-discovery-with-mesos-dns.md:
--------------------------------------------------------------------------------
 1 | ---
 2 | layout: post
 3 | title:  "Service discovery with Mesos DNS"
 4 | categories: docker
 5 | author: thomas-maurice
 6 | lang: en
 7 | ---
 8 | 
 9 | 
10 | 
11 | This tutorial introduces how to use the Mesos DNS service discovery with OVH PaaS Docker.
12 | 
13 | 
14 | 
15 | # Motivation
16 | 
17 | As you might have noticed, in the OVH PaaS Docker, each container has a private IP address, which is unique within a given cluster. You would
18 | logically want to make two of your containers communicate without having to get out on the Internet and go through the load balancer.
19 | The problem is that the IP addresses are assigned by Mesos in a quite unpredictable way. To fix this issue we now enable you to access your
20 | containers with DNS records refreshed on a regular basis.
21 | 
22 | # Introducing Mesos DNS
23 | [Mesos DNS](https://github.com/mesosphere/mesos-dns) is a nice piece of software developped by Mesosphere which enables service discovery within
24 | a Mesos cluster. It acts like a DNS server, and maintains an up to date list of *A* and *SRV* records to allow your containers to speak with one another
25 | even though they might move between hosts at any time.
26 | 
27 | An important information to understand is that if you scale your containers, Mesos DNS will return you several A fields for the service you wish
28 | to reach. You have absolutely no idempotence guarantee: the same request might not hit the same container twice.
29 | 
30 | # Demo time
31 | As a small demonstration is always better than a long speech, let's go! We shall assume the following:
32 | 
33 |  * My stack name is `docker-mt42-1`
34 |  * I have an `api` service, scaled to 3
35 |  * I want to reach it from another container, for the sake of the demo we will just assume I have a shell opened inside to do stuff.
36 | 
37 | The DNS names of the services are formed as it follows :
38 | 
39 | ```
40 | <service-name>-<stack-name>.customers-marathon.mesos
41 | ```
42 | 
43 | For simplicity reasons, you can ommit the `customers-marathon.mesos` part. So following this construction if I want to access my `api` service
44 | all I have to do is:
45 | 
46 | ```
47 | root@c0c899be1d7f:/# host api-docker-mt42-1
48 | api-docker-mt42-1.customers-marathon.mesos has address 172.16.78.5
49 | api-docker-mt42-1.customers-marathon.mesos has address 172.16.78.3
50 | api-docker-mt42-1.customers-marathon.mesos has address 172.16.78.6
51 | ```
52 | 
53 | And unsurprisingly it works!
54 | 
55 | Let's try a little curl:
56 | 
57 | ```
58 | root@c0c899be1d7f:/# curl api-docker-mt42-1:5000
59 | Hello world!
60 | ```
61 | 
62 | Nice !
63 | 
64 | Note that when talking to the IP addresses of your containers, you can ignore the hostPort field given by the Marathon UI, since the container is
65 | exposed directly on the internal network. This said, other customers, even though they are able to get your container's IP
66 | addresses in some way, are unable to access your containers. Each portion of the network being dedicated to a customer, it is isolated from
67 | the rest.
68 | 
69 | Happy marathon!
70 | 
71 | # Further readings
72 | [Mesos DNS naming conventions](https://mesosphere.github.io/mesos-dns/docs/naming.html)
73 | 
74 | 


--------------------------------------------------------------------------------
/en/_posts/2016-11-07-using-a-private-registry.md:
--------------------------------------------------------------------------------
 1 | ---
 2 | layout: post
 3 | title:  "Using a private Docker registry"
 4 | categories: docker
 5 | author: brouberol
 6 | lang: en
 7 | ---
 8 | 
 9 | In this tutorial, we'll see how to link your Marathon to a private Docker registry, and enable authenticated docker pulls.
10 | 
11 | # Adding private Docker registry credentials to your stack
12 | 
13 | The only required step to be able to pull docker images from a private registry is linking the registry credentials to your stack. You can perform this operation using the [Manager](https://www.ovh.com/manager/sunrise/containers/index.html#/containers) or the [API](https://api.ovh.com/console/#/caas/containers/%7BserviceName%7D/registry/credentials#POST).
14 | 
15 | For example, we can link your private Docker Hub account to your stack:
16 | 
17 | ![Adding private registry credentials](/kb/images/2016-11-07-using-a-private-registry/private-registry.png)
18 | 
19 | *Note*: If you're looking for the registry URL, you can have a look in the `~/.docker/config.json` configuration file, on a machine where you've already performed the `docker login` operation.
20 | 
21 | Once you've added your credentials, we'll automatically deploy them onto all your slaves, and they will automatically be used when pulling the docker image. Contrary to what the official [Marathon documentation](https://mesosphere.github.io/marathon/docs/native-docker-private-registry.html) states, you don't have to include a link to your credentials when deploying application to Marathon. We're taking care of this for you.
22 | 
23 | That's it, nothing else!
24 | 
25 | *Note*: you can link credentials to any number of different private registries to your stack. Furthermore, OVH will soon provide you with an in-house authenticated Docker registry.
26 | 
27 | 


--------------------------------------------------------------------------------
/en/index.html:
--------------------------------------------------------------------------------
1 | ---
2 | layout: home 
3 | lang: en
4 | ---
5 | 
6 | 


--------------------------------------------------------------------------------
/feed.xml:
--------------------------------------------------------------------------------
 1 | ---
 2 | layout: none
 3 | ---
 4 | <?xml version="1.0" encoding="UTF-8"?>
 5 | <rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
 6 |   <channel>
 7 |     <title>{{ site.title | xml_escape }}</title>
 8 |     <description>{{ site.description | xml_escape }}</description>
 9 |     <link>{{ site.url }}{{ site.baseurl }}/</link>
10 |     <atom:link href="{{ "/feed.xml" | prepend: site.baseurl | prepend: site.url }}" rel="self" type="application/rss+xml" />
11 |     <pubDate>{{ site.time | date_to_rfc822 }}</pubDate>
12 |     <lastBuildDate>{{ site.time | date_to_rfc822 }}</lastBuildDate>
13 |     <generator>Jekyll v{{ jekyll.version }}</generator>
14 |     {% for post in site.posts limit:10 %}
15 |       <item>
16 |         <title>{{ post.title | xml_escape }}</title>
17 |         <description>{{ post.excerpt | strip_html | xml_escape }}</description>
18 |         <author>{{ post.author | xml_escape }}</author>
19 |         <pubDate>{{ post.date | date_to_rfc822 }}</pubDate>
20 |         <link>{{ post.url | prepend: site.baseurl | prepend: site.url }}</link>
21 |         <guid isPermaLink="true">{{ post.url | prepend: site.baseurl | prepend: site.url }}</guid>
22 |         {% for tag in post.tags %}
23 |         <category>{{ tag | xml_escape }}</category>
24 |         {% endfor %}
25 |         {% for cat in post.categories %}
26 |         <category>{{ cat | xml_escape }}</category>
27 |         {% endfor %}
28 |       </item>
29 |     {% endfor %}
30 |   </channel>
31 | </rss>
32 | 


--------------------------------------------------------------------------------
/images/2014-07-28-deploy-load-balanced-wordpress/nfs-word-relation.png:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/ovhlabs/knowledge-base/b6339a6f5d858fcee972f4c4a451870bf7464d26/images/2014-07-28-deploy-load-balanced-wordpress/nfs-word-relation.png


--------------------------------------------------------------------------------
/images/2014-07-28-deploy-load-balanced-wordpress/structure.png:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/ovhlabs/knowledge-base/b6339a6f5d858fcee972f4c4a451870bf7464d26/images/2014-07-28-deploy-load-balanced-wordpress/structure.png


--------------------------------------------------------------------------------
/images/2014-07-28-deploy-load-balanced-wordpress/word-mysql-rel.png:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/ovhlabs/knowledge-base/b6339a6f5d858fcee972f4c4a451870bf7464d26/images/2014-07-28-deploy-load-balanced-wordpress/word-mysql-rel.png


--------------------------------------------------------------------------------
/images/2014-07-28-deploy-load-balanced-wordpress/wordpress.png:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/ovhlabs/knowledge-base/b6339a6f5d858fcee972f4c4a451870bf7464d26/images/2014-07-28-deploy-load-balanced-wordpress/wordpress.png


--------------------------------------------------------------------------------
/images/2014-09-09-create-local-network/net_list.png:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/ovhlabs/knowledge-base/b6339a6f5d858fcee972f4c4a451870bf7464d26/images/2014-09-09-create-local-network/net_list.png


--------------------------------------------------------------------------------
/images/2014-09-09-create-local-network/network_name.png:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/ovhlabs/knowledge-base/b6339a6f5d858fcee972f4c4a451870bf7464d26/images/2014-09-09-create-local-network/network_name.png


--------------------------------------------------------------------------------
/images/2014-09-09-create-local-network/schema.png:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/ovhlabs/knowledge-base/b6339a6f5d858fcee972f4c4a451870bf7464d26/images/2014-09-09-create-local-network/schema.png


--------------------------------------------------------------------------------
/images/2014-09-09-create-local-network/subnet.png:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/ovhlabs/knowledge-base/b6339a6f5d858fcee972f4c4a451870bf7464d26/images/2014-09-09-create-local-network/subnet.png


--------------------------------------------------------------------------------
/images/2014-09-09-create-local-network/subnet_details.png:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/ovhlabs/knowledge-base/b6339a6f5d858fcee972f4c4a451870bf7464d26/images/2014-09-09-create-local-network/subnet_details.png


--------------------------------------------------------------------------------
/images/2014-09-25-how-to-install-openvpn-access-server-on-ubuntu-14.04/openvpn1.jpg:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/ovhlabs/knowledge-base/b6339a6f5d858fcee972f4c4a451870bf7464d26/images/2014-09-25-how-to-install-openvpn-access-server-on-ubuntu-14.04/openvpn1.jpg


--------------------------------------------------------------------------------
/images/2014-09-25-how-to-install-openvpn-access-server-on-ubuntu-14.04/openvpn2.jpg:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/ovhlabs/knowledge-base/b6339a6f5d858fcee972f4c4a451870bf7464d26/images/2014-09-25-how-to-install-openvpn-access-server-on-ubuntu-14.04/openvpn2.jpg


--------------------------------------------------------------------------------
/images/2014-09-25-how-to-install-openvpn-access-server-on-ubuntu-14.04/openvpn3.jpg:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/ovhlabs/knowledge-base/b6339a6f5d858fcee972f4c4a451870bf7464d26/images/2014-09-25-how-to-install-openvpn-access-server-on-ubuntu-14.04/openvpn3.jpg


--------------------------------------------------------------------------------
/images/2014-09-25-how-to-install-openvpn-access-server-on-ubuntu-14.04/openvpn4.png:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/ovhlabs/knowledge-base/b6339a6f5d858fcee972f4c4a451870bf7464d26/images/2014-09-25-how-to-install-openvpn-access-server-on-ubuntu-14.04/openvpn4.png


--------------------------------------------------------------------------------
/images/2014-10-01-create-ssh-keys/putty.png:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/ovhlabs/knowledge-base/b6339a6f5d858fcee972f4c4a451870bf7464d26/images/2014-10-01-create-ssh-keys/putty.png


--------------------------------------------------------------------------------
/images/2014-10-01-create-ssh-keys/puttygen.png:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/ovhlabs/knowledge-base/b6339a6f5d858fcee972f4c4a451870bf7464d26/images/2014-10-01-create-ssh-keys/puttygen.png


--------------------------------------------------------------------------------
/images/2014-10-06-power8/htop.png:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/ovhlabs/knowledge-base/b6339a6f5d858fcee972f4c4a451870bf7464d26/images/2014-10-06-power8/htop.png


--------------------------------------------------------------------------------
/images/2014-11-07-private-network-nat/layout.png:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/ovhlabs/knowledge-base/b6339a6f5d858fcee972f4c4a451870bf7464d26/images/2014-11-07-private-network-nat/layout.png


--------------------------------------------------------------------------------
/images/2014-11-07-private-network-nat/network-step1.png:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/ovhlabs/knowledge-base/b6339a6f5d858fcee972f4c4a451870bf7464d26/images/2014-11-07-private-network-nat/network-step1.png


--------------------------------------------------------------------------------
/images/2014-11-07-private-network-nat/network-step2.png:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/ovhlabs/knowledge-base/b6339a6f5d858fcee972f4c4a451870bf7464d26/images/2014-11-07-private-network-nat/network-step2.png


--------------------------------------------------------------------------------
/images/2014-11-07-private-network-nat/network-step3.png:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/ovhlabs/knowledge-base/b6339a6f5d858fcee972f4c4a451870bf7464d26/images/2014-11-07-private-network-nat/network-step3.png


--------------------------------------------------------------------------------
/images/2014-11-07-private-network-nat/network-step4.png:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/ovhlabs/knowledge-base/b6339a6f5d858fcee972f4c4a451870bf7464d26/images/2014-11-07-private-network-nat/network-step4.png


--------------------------------------------------------------------------------
/images/2014-11-17-send-reliable-emails-from-your-runabove-instance-with-mailjet/mailjet.png:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/ovhlabs/knowledge-base/b6339a6f5d858fcee972f4c4a451870bf7464d26/images/2014-11-17-send-reliable-emails-from-your-runabove-instance-with-mailjet/mailjet.png


--------------------------------------------------------------------------------
/images/2014-12-05-how-to-deploy-a-shipyard-cluster-on-runabove/shipyard-login.png:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/ovhlabs/knowledge-base/b6339a6f5d858fcee972f4c4a451870bf7464d26/images/2014-12-05-how-to-deploy-a-shipyard-cluster-on-runabove/shipyard-login.png


--------------------------------------------------------------------------------
/images/2014-12-12-docker-in-5-minutes-on-runabove-with-docker-machine/docker-logo.png:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/ovhlabs/knowledge-base/b6339a6f5d858fcee972f4c4a451870bf7464d26/images/2014-12-12-docker-in-5-minutes-on-runabove-with-docker-machine/docker-logo.png


--------------------------------------------------------------------------------
/images/2014-12-29-security-groups/add-rule.png:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/ovhlabs/knowledge-base/b6339a6f5d858fcee972f4c4a451870bf7464d26/images/2014-12-29-security-groups/add-rule.png


--------------------------------------------------------------------------------
/images/2015-01-14-running-wordpress-on-sailabove/containers.png:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/ovhlabs/knowledge-base/b6339a6f5d858fcee972f4c4a451870bf7464d26/images/2015-01-14-running-wordpress-on-sailabove/containers.png


--------------------------------------------------------------------------------
/images/2015-01-29-attach-volume/attach.png:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/ovhlabs/knowledge-base/b6339a6f5d858fcee972f4c4a451870bf7464d26/images/2015-01-29-attach-volume/attach.png


--------------------------------------------------------------------------------
/images/2015-01-29-attach-volume/create.png:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/ovhlabs/knowledge-base/b6339a6f5d858fcee972f4c4a451870bf7464d26/images/2015-01-29-attach-volume/create.png


--------------------------------------------------------------------------------
/images/2015-01-29-attach-volume/edit-attachments.png:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/ovhlabs/knowledge-base/b6339a6f5d858fcee972f4c4a451870bf7464d26/images/2015-01-29-attach-volume/edit-attachments.png


--------------------------------------------------------------------------------
/images/2015-01-29-attach-volume/windows-disk-management.png:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/ovhlabs/knowledge-base/b6339a6f5d858fcee972f4c4a451870bf7464d26/images/2015-01-29-attach-volume/windows-disk-management.png


--------------------------------------------------------------------------------
/images/2015-01-29-attach-volume/windows-drives.png:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/ovhlabs/knowledge-base/b6339a6f5d858fcee972f4c4a451870bf7464d26/images/2015-01-29-attach-volume/windows-drives.png


--------------------------------------------------------------------------------
/images/2015-01-29-attach-volume/windows-new.png:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/ovhlabs/knowledge-base/b6339a6f5d858fcee972f4c4a451870bf7464d26/images/2015-01-29-attach-volume/windows-new.png


--------------------------------------------------------------------------------
/images/2015-01-29-attach-volume/windows-online.png:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/ovhlabs/knowledge-base/b6339a6f5d858fcee972f4c4a451870bf7464d26/images/2015-01-29-attach-volume/windows-online.png


--------------------------------------------------------------------------------
/images/2015-03-12-jekyll-and-swift-object-storage/runabove-openstack-rc.png:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/ovhlabs/knowledge-base/b6339a6f5d858fcee972f4c4a451870bf7464d26/images/2015-03-12-jekyll-and-swift-object-storage/runabove-openstack-rc.png


--------------------------------------------------------------------------------
/images/2015-08-10-how-to-manage-iot-applications-using-runabove-manager/application-creation-page.png:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/ovhlabs/knowledge-base/b6339a6f5d858fcee972f4c4a451870bf7464d26/images/2015-08-10-how-to-manage-iot-applications-using-runabove-manager/application-creation-page.png


--------------------------------------------------------------------------------
/images/2015-08-10-how-to-manage-iot-applications-using-runabove-manager/application-page.png:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/ovhlabs/knowledge-base/b6339a6f5d858fcee972f4c4a451870bf7464d26/images/2015-08-10-how-to-manage-iot-applications-using-runabove-manager/application-page.png


--------------------------------------------------------------------------------
/images/2015-08-10-how-to-manage-iot-applications-using-runabove-manager/empty-application-page.png:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/ovhlabs/knowledge-base/b6339a6f5d858fcee972f4c4a451870bf7464d26/images/2015-08-10-how-to-manage-iot-applications-using-runabove-manager/empty-application-page.png


--------------------------------------------------------------------------------
/images/2015-08-10-how-to-manage-iot-applications-using-runabove-manager/token-creation-page.png:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/ovhlabs/knowledge-base/b6339a6f5d858fcee972f4c4a451870bf7464d26/images/2015-08-10-how-to-manage-iot-applications-using-runabove-manager/token-creation-page.png


--------------------------------------------------------------------------------
/images/2015-08-10-how-to-manage-iot-applications-using-runabove-manager/token-list.png:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/ovhlabs/knowledge-base/b6339a6f5d858fcee972f4c4a451870bf7464d26/images/2015-08-10-how-to-manage-iot-applications-using-runabove-manager/token-list.png


--------------------------------------------------------------------------------
/images/2015-08-10-how-to-manage-iot-applications-using-runabove-manager/token-page.png:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/ovhlabs/knowledge-base/b6339a6f5d858fcee972f4c4a451870bf7464d26/images/2015-08-10-how-to-manage-iot-applications-using-runabove-manager/token-page.png


--------------------------------------------------------------------------------
/images/2015-10-13-how-to-use-arm-lab/step1.png:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/ovhlabs/knowledge-base/b6339a6f5d858fcee972f4c4a451870bf7464d26/images/2015-10-13-how-to-use-arm-lab/step1.png


--------------------------------------------------------------------------------
/images/2015-10-13-how-to-use-arm-lab/step2.png:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/ovhlabs/knowledge-base/b6339a6f5d858fcee972f4c4a451870bf7464d26/images/2015-10-13-how-to-use-arm-lab/step2.png


--------------------------------------------------------------------------------
/images/2015-10-13-how-to-use-arm-lab/step3.png:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/ovhlabs/knowledge-base/b6339a6f5d858fcee972f4c4a451870bf7464d26/images/2015-10-13-how-to-use-arm-lab/step3.png


--------------------------------------------------------------------------------
/images/2015-10-13-how-to-use-arm-lab/step4.png:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/ovhlabs/knowledge-base/b6339a6f5d858fcee972f4c4a451870bf7464d26/images/2015-10-13-how-to-use-arm-lab/step4.png


--------------------------------------------------------------------------------
/images/2015-10-13-how-to-use-arm-lab/step5.png:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/ovhlabs/knowledge-base/b6339a6f5d858fcee972f4c4a451870bf7464d26/images/2015-10-13-how-to-use-arm-lab/step5.png


--------------------------------------------------------------------------------
/images/2015-10-13-how-to-use-arm-lab/step6.png:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/ovhlabs/knowledge-base/b6339a6f5d858fcee972f4c4a451870bf7464d26/images/2015-10-13-how-to-use-arm-lab/step6.png


--------------------------------------------------------------------------------
/images/2015-10-13-how-to-use-arm-lab/step7.png:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/ovhlabs/knowledge-base/b6339a6f5d858fcee972f4c4a451870bf7464d26/images/2015-10-13-how-to-use-arm-lab/step7.png


--------------------------------------------------------------------------------
/images/2015-10-13-how-to-use-arm-lab/step8.png:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/ovhlabs/knowledge-base/b6339a6f5d858fcee972f4c4a451870bf7464d26/images/2015-10-13-how-to-use-arm-lab/step8.png


--------------------------------------------------------------------------------
/images/2015-10-13-how-to-use-arm-lab/step9.png:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/ovhlabs/knowledge-base/b6339a6f5d858fcee972f4c4a451870bf7464d26/images/2015-10-13-how-to-use-arm-lab/step9.png


--------------------------------------------------------------------------------
/images/2015-10-13-how-to-use-vps-hdd-lab/step1.png:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/ovhlabs/knowledge-base/b6339a6f5d858fcee972f4c4a451870bf7464d26/images/2015-10-13-how-to-use-vps-hdd-lab/step1.png


--------------------------------------------------------------------------------
/images/2015-10-13-how-to-use-vps-hdd-lab/step2.png:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/ovhlabs/knowledge-base/b6339a6f5d858fcee972f4c4a451870bf7464d26/images/2015-10-13-how-to-use-vps-hdd-lab/step2.png


--------------------------------------------------------------------------------
/images/2015-10-13-how-to-use-vps-hdd-lab/step3.png:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/ovhlabs/knowledge-base/b6339a6f5d858fcee972f4c4a451870bf7464d26/images/2015-10-13-how-to-use-vps-hdd-lab/step3.png


--------------------------------------------------------------------------------
/images/2015-10-13-how-to-use-vps-hdd-lab/step4.png:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/ovhlabs/knowledge-base/b6339a6f5d858fcee972f4c4a451870bf7464d26/images/2015-10-13-how-to-use-vps-hdd-lab/step4.png


--------------------------------------------------------------------------------
/images/2015-10-16-how-to-serial-console-arm-instance/goto_dashboard.png:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/ovhlabs/knowledge-base/b6339a6f5d858fcee972f4c4a451870bf7464d26/images/2015-10-16-how-to-serial-console-arm-instance/goto_dashboard.png


--------------------------------------------------------------------------------
/images/2015-10-16-how-to-serial-console-arm-instance/no_console_log.png:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/ovhlabs/knowledge-base/b6339a6f5d858fcee972f4c4a451870bf7464d26/images/2015-10-16-how-to-serial-console-arm-instance/no_console_log.png


--------------------------------------------------------------------------------
/images/2015-10-16-how-to-serial-console-arm-instance/no_vnc.png:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/ovhlabs/knowledge-base/b6339a6f5d858fcee972f4c4a451870bf7464d26/images/2015-10-16-how-to-serial-console-arm-instance/no_vnc.png


--------------------------------------------------------------------------------
/images/2015-10-16-how-to-serial-console-arm-instance/openstack_creds.png:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/ovhlabs/knowledge-base/b6339a6f5d858fcee972f4c4a451870bf7464d26/images/2015-10-16-how-to-serial-console-arm-instance/openstack_creds.png


--------------------------------------------------------------------------------
/images/2015-10-16-how-to-serial-console-arm-instance/serial_console.png:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/ovhlabs/knowledge-base/b6339a6f5d858fcee972f4c4a451870bf7464d26/images/2015-10-16-how-to-serial-console-arm-instance/serial_console.png


--------------------------------------------------------------------------------
/images/2015-10-16-how-to-serial-console-arm-instance/source_creds.png:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/ovhlabs/knowledge-base/b6339a6f5d858fcee972f4c4a451870bf7464d26/images/2015-10-16-how-to-serial-console-arm-instance/source_creds.png


--------------------------------------------------------------------------------
/images/2015-11-23-use-sailabove-webhook/container-states.jpg:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/ovhlabs/knowledge-base/b6339a6f5d858fcee972f4c4a451870bf7464d26/images/2015-11-23-use-sailabove-webhook/container-states.jpg


--------------------------------------------------------------------------------
/images/2015-11-24-how-to-start-simple-puppet-master/puppetboard.png:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/ovhlabs/knowledge-base/b6339a6f5d858fcee972f4c4a451870bf7464d26/images/2015-11-24-how-to-start-simple-puppet-master/puppetboard.png


--------------------------------------------------------------------------------
/images/2015-11-28-migrate-from-runabove-to-public-cloud/horizon_security_panel.jpg:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/ovhlabs/knowledge-base/b6339a6f5d858fcee972f4c4a451870bf7464d26/images/2015-11-28-migrate-from-runabove-to-public-cloud/horizon_security_panel.jpg


--------------------------------------------------------------------------------
/images/2015-11-28-migrate-from-runabove-to-public-cloud/runabove_menu.jpg:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/ovhlabs/knowledge-base/b6339a6f5d858fcee972f4c4a451870bf7464d26/images/2015-11-28-migrate-from-runabove-to-public-cloud/runabove_menu.jpg


--------------------------------------------------------------------------------
/images/2015-12-08-start-puppet-master/certificate.png:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/ovhlabs/knowledge-base/b6339a6f5d858fcee972f4c4a451870bf7464d26/images/2015-12-08-start-puppet-master/certificate.png


--------------------------------------------------------------------------------
/images/2015-12-08-start-puppet-master/create-master.png:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/ovhlabs/knowledge-base/b6339a6f5d858fcee972f4c4a451870bf7464d26/images/2015-12-08-start-puppet-master/create-master.png


--------------------------------------------------------------------------------
/images/2015-12-08-start-puppet-master/deploykey.png:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/ovhlabs/knowledge-base/b6339a6f5d858fcee972f4c4a451870bf7464d26/images/2015-12-08-start-puppet-master/deploykey.png


--------------------------------------------------------------------------------
/images/2015-12-10-create-mysql-managed-stack/activate.png:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/ovhlabs/knowledge-base/b6339a6f5d858fcee972f4c4a451870bf7464d26/images/2015-12-10-create-mysql-managed-stack/activate.png


--------------------------------------------------------------------------------
/images/2015-12-10-create-mysql-managed-stack/cluster_status.png:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/ovhlabs/knowledge-base/b6339a6f5d858fcee972f4c4a451870bf7464d26/images/2015-12-10-create-mysql-managed-stack/cluster_status.png


--------------------------------------------------------------------------------
/images/2015-12-10-create-mysql-managed-stack/delete_stack1.png:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/ovhlabs/knowledge-base/b6339a6f5d858fcee972f4c4a451870bf7464d26/images/2015-12-10-create-mysql-managed-stack/delete_stack1.png


--------------------------------------------------------------------------------
/images/2015-12-10-create-mysql-managed-stack/delete_stack2.png:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/ovhlabs/knowledge-base/b6339a6f5d858fcee972f4c4a451870bf7464d26/images/2015-12-10-create-mysql-managed-stack/delete_stack2.png


--------------------------------------------------------------------------------
/images/2015-12-10-create-mysql-managed-stack/menu_managed.png:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/ovhlabs/knowledge-base/b6339a6f5d858fcee972f4c4a451870bf7464d26/images/2015-12-10-create-mysql-managed-stack/menu_managed.png


--------------------------------------------------------------------------------
/images/2015-12-10-create-mysql-managed-stack/new_stack.png:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/ovhlabs/knowledge-base/b6339a6f5d858fcee972f4c4a451870bf7464d26/images/2015-12-10-create-mysql-managed-stack/new_stack.png


--------------------------------------------------------------------------------
/images/2015-12-10-create-mysql-managed-stack/signup.png:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/ovhlabs/knowledge-base/b6339a6f5d858fcee972f4c4a451870bf7464d26/images/2015-12-10-create-mysql-managed-stack/signup.png


--------------------------------------------------------------------------------
/images/2015-12-10-create-mysql-managed-stack/stack_details.png:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/ovhlabs/knowledge-base/b6339a6f5d858fcee972f4c4a451870bf7464d26/images/2015-12-10-create-mysql-managed-stack/stack_details.png


--------------------------------------------------------------------------------
/images/2015-12-10-create-mysql-managed-stack/start.png:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/ovhlabs/knowledge-base/b6339a6f5d858fcee972f4c4a451870bf7464d26/images/2015-12-10-create-mysql-managed-stack/start.png


--------------------------------------------------------------------------------
/images/2015-12-10-create-mysql-managed-stack/status_active.png:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/ovhlabs/knowledge-base/b6339a6f5d858fcee972f4c4a451870bf7464d26/images/2015-12-10-create-mysql-managed-stack/status_active.png


--------------------------------------------------------------------------------
/images/2016-01-20-create-sqlserver-instance/AddDatabase1.png:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/ovhlabs/knowledge-base/b6339a6f5d858fcee972f4c4a451870bf7464d26/images/2016-01-20-create-sqlserver-instance/AddDatabase1.png


--------------------------------------------------------------------------------
/images/2016-01-20-create-sqlserver-instance/AddDatabase2.png:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/ovhlabs/knowledge-base/b6339a6f5d858fcee972f4c4a451870bf7464d26/images/2016-01-20-create-sqlserver-instance/AddDatabase2.png


--------------------------------------------------------------------------------
/images/2016-01-20-create-sqlserver-instance/ExplorerSql.png:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/ovhlabs/knowledge-base/b6339a6f5d858fcee972f4c4a451870bf7464d26/images/2016-01-20-create-sqlserver-instance/ExplorerSql.png


--------------------------------------------------------------------------------
/images/2016-01-20-create-sqlserver-instance/NewSqlServer.png:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/ovhlabs/knowledge-base/b6339a6f5d858fcee972f4c4a451870bf7464d26/images/2016-01-20-create-sqlserver-instance/NewSqlServer.png


--------------------------------------------------------------------------------
/images/2016-01-20-create-sqlserver-instance/NewSqlServer2.png:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/ovhlabs/knowledge-base/b6339a6f5d858fcee972f4c4a451870bf7464d26/images/2016-01-20-create-sqlserver-instance/NewSqlServer2.png


--------------------------------------------------------------------------------
/images/2016-01-20-create-sqlserver-instance/NewSqlServer3.png:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/ovhlabs/knowledge-base/b6339a6f5d858fcee972f4c4a451870bf7464d26/images/2016-01-20-create-sqlserver-instance/NewSqlServer3.png


--------------------------------------------------------------------------------
/images/2016-01-20-create-sqlserver-instance/connection.png:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/ovhlabs/knowledge-base/b6339a6f5d858fcee972f4c4a451870bf7464d26/images/2016-01-20-create-sqlserver-instance/connection.png


--------------------------------------------------------------------------------
/images/2016-01-20-create-sqlserver-instance/databaseActions.png:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/ovhlabs/knowledge-base/b6339a6f5d858fcee972f4c4a451870bf7464d26/images/2016-01-20-create-sqlserver-instance/databaseActions.png


--------------------------------------------------------------------------------
/images/2016-01-20-create-sqlserver-instance/signup.png:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/ovhlabs/knowledge-base/b6339a6f5d858fcee972f4c4a451870bf7464d26/images/2016-01-20-create-sqlserver-instance/signup.png


--------------------------------------------------------------------------------
/images/2016-01-20-create-sqlserver-instance/start.png:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/ovhlabs/knowledge-base/b6339a6f5d858fcee972f4c4a451870bf7464d26/images/2016-01-20-create-sqlserver-instance/start.png


--------------------------------------------------------------------------------
/images/2016-01-20-create-sqlserver-instance/wapPortal.png:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/ovhlabs/knowledge-base/b6339a6f5d858fcee972f4c4a451870bf7464d26/images/2016-01-20-create-sqlserver-instance/wapPortal.png


--------------------------------------------------------------------------------
/images/2016-02-24-how-to-log-your-linux/search.png:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/ovhlabs/knowledge-base/b6339a6f5d858fcee972f4c4a451870bf7464d26/images/2016-02-24-how-to-log-your-linux/search.png


--------------------------------------------------------------------------------
/images/2016-02-25-android-nxlog/graylog.png:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/ovhlabs/knowledge-base/b6339a6f5d858fcee972f4c4a451870bf7464d26/images/2016-02-25-android-nxlog/graylog.png


--------------------------------------------------------------------------------
/images/2016-02-25-android-nxlog/screen-pid.png:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/ovhlabs/knowledge-base/b6339a6f5d858fcee972f4c4a451870bf7464d26/images/2016-02-25-android-nxlog/screen-pid.png


--------------------------------------------------------------------------------
/images/2016-02-25-apache-logs/apache-logs.png:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/ovhlabs/knowledge-base/b6339a6f5d858fcee972f4c4a451870bf7464d26/images/2016-02-25-apache-logs/apache-logs.png


--------------------------------------------------------------------------------
/images/2016-02-25-apache-logs/cheatsheet.png:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/ovhlabs/knowledge-base/b6339a6f5d858fcee972f4c4a451870bf7464d26/images/2016-02-25-apache-logs/cheatsheet.png


--------------------------------------------------------------------------------
/images/2016-02-25-filebeat-logs/beats_graylog.png:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/ovhlabs/knowledge-base/b6339a6f5d858fcee972f4c4a451870bf7464d26/images/2016-02-25-filebeat-logs/beats_graylog.png


--------------------------------------------------------------------------------
/images/2016-02-25-filebeat-logs/filter_graylog.png:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/ovhlabs/knowledge-base/b6339a6f5d858fcee972f4c4a451870bf7464d26/images/2016-02-25-filebeat-logs/filter_graylog.png


--------------------------------------------------------------------------------
/images/2016-02-25-windows-nxlog/graylog.png:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/ovhlabs/knowledge-base/b6339a6f5d858fcee972f4c4a451870bf7464d26/images/2016-02-25-windows-nxlog/graylog.png


--------------------------------------------------------------------------------
/images/2016-02-25-windows-nxlog/panel_config.png:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/ovhlabs/knowledge-base/b6339a6f5d858fcee972f4c4a451870bf7464d26/images/2016-02-25-windows-nxlog/panel_config.png


--------------------------------------------------------------------------------
/images/2016-02-27-logstash-input/config_logstash_1.png:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/ovhlabs/knowledge-base/b6339a6f5d858fcee972f4c4a451870bf7464d26/images/2016-02-27-logstash-input/config_logstash_1.png


--------------------------------------------------------------------------------
/images/2016-02-27-logstash-input/filter_section.png:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/ovhlabs/knowledge-base/b6339a6f5d858fcee972f4c4a451870bf7464d26/images/2016-02-27-logstash-input/filter_section.png


--------------------------------------------------------------------------------
/images/2016-02-27-logstash-input/input_section.png:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/ovhlabs/knowledge-base/b6339a6f5d858fcee972f4c4a451870bf7464d26/images/2016-02-27-logstash-input/input_section.png


--------------------------------------------------------------------------------
/images/2016-02-27-logstash-input/input_start.png:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/ovhlabs/knowledge-base/b6339a6f5d858fcee972f4c4a451870bf7464d26/images/2016-02-27-logstash-input/input_start.png


--------------------------------------------------------------------------------
/images/2016-02-27-logstash-input/local_logstash_graylog.png:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/ovhlabs/knowledge-base/b6339a6f5d858fcee972f4c4a451870bf7464d26/images/2016-02-27-logstash-input/local_logstash_graylog.png


--------------------------------------------------------------------------------
/images/2016-02-27-logstash-input/logstash_created.png:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/ovhlabs/knowledge-base/b6339a6f5d858fcee972f4c4a451870bf7464d26/images/2016-02-27-logstash-input/logstash_created.png


--------------------------------------------------------------------------------
/images/2016-02-27-logstash-input/logstash_ssl.png:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/ovhlabs/knowledge-base/b6339a6f5d858fcee972f4c4a451870bf7464d26/images/2016-02-27-logstash-input/logstash_ssl.png


--------------------------------------------------------------------------------
/images/2016-02-27-logstash-input/network-input.png:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/ovhlabs/knowledge-base/b6339a6f5d858fcee972f4c4a451870bf7464d26/images/2016-02-27-logstash-input/network-input.png


--------------------------------------------------------------------------------
/images/2016-02-27-logstash-input/stream_sub.png:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/ovhlabs/knowledge-base/b6339a6f5d858fcee972f4c4a451870bf7464d26/images/2016-02-27-logstash-input/stream_sub.png


--------------------------------------------------------------------------------
/images/2016-02-27-logstash-input/test_success.png:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/ovhlabs/knowledge-base/b6339a6f5d858fcee972f4c4a451870bf7464d26/images/2016-02-27-logstash-input/test_success.png


--------------------------------------------------------------------------------
/images/2016-02-27-tokens-paas-logs/postman_1.png:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/ovhlabs/knowledge-base/b6339a6f5d858fcee972f4c4a451870bf7464d26/images/2016-02-27-tokens-paas-logs/postman_1.png


--------------------------------------------------------------------------------
/images/2016-02-27-tokens-paas-logs/rest_easy.png:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/ovhlabs/knowledge-base/b6339a6f5d858fcee972f4c4a451870bf7464d26/images/2016-02-27-tokens-paas-logs/rest_easy.png


--------------------------------------------------------------------------------
/images/2016-02-28-field-naming-conventions/bytes.png:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/ovhlabs/knowledge-base/b6339a6f5d858fcee972f4c4a451870bf7464d26/images/2016-02-28-field-naming-conventions/bytes.png


--------------------------------------------------------------------------------
/images/2016-02-28-field-naming-conventions/reserved_keywords.png:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/ovhlabs/knowledge-base/b6339a6f5d858fcee972f4c4a451870bf7464d26/images/2016-02-28-field-naming-conventions/reserved_keywords.png


--------------------------------------------------------------------------------
/images/2016-02-28-field-naming-conventions/suffixes.png:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/ovhlabs/knowledge-base/b6339a6f5d858fcee972f4c4a451870bf7464d26/images/2016-02-28-field-naming-conventions/suffixes.png


--------------------------------------------------------------------------------
/images/2016-02-28-using-grafana-with-laas/alias.png:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/ovhlabs/knowledge-base/b6339a6f5d858fcee972f4c4a451870bf7464d26/images/2016-02-28-using-grafana-with-laas/alias.png


--------------------------------------------------------------------------------
/images/2016-02-28-using-grafana-with-laas/datasource.png:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/ovhlabs/knowledge-base/b6339a6f5d858fcee972f4c4a451870bf7464d26/images/2016-02-28-using-grafana-with-laas/datasource.png


--------------------------------------------------------------------------------
/images/2016-02-28-using-grafana-with-laas/grafana.png:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/ovhlabs/knowledge-base/b6339a6f5d858fcee972f4c4a451870bf7464d26/images/2016-02-28-using-grafana-with-laas/grafana.png


--------------------------------------------------------------------------------
/images/2016-02-28-using-timelion-with-laas.md/dash.png:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/ovhlabs/knowledge-base/b6339a6f5d858fcee972f4c4a451870bf7464d26/images/2016-02-28-using-timelion-with-laas.md/dash.png


--------------------------------------------------------------------------------
/images/2016-02-28-using-timelion-with-laas.md/timelion-2.png:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/ovhlabs/knowledge-base/b6339a6f5d858fcee972f4c4a451870bf7464d26/images/2016-02-28-using-timelion-with-laas.md/timelion-2.png


--------------------------------------------------------------------------------
/images/2016-02-28-using-timelion-with-laas.md/timelion.png:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/ovhlabs/knowledge-base/b6339a6f5d858fcee972f4c4a451870bf7464d26/images/2016-02-28-using-timelion-with-laas.md/timelion.png


--------------------------------------------------------------------------------
/images/2016-02-29-using-kibana-with-laas/alias.png:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/ovhlabs/knowledge-base/b6339a6f5d858fcee972f4c4a451870bf7464d26/images/2016-02-29-using-kibana-with-laas/alias.png


--------------------------------------------------------------------------------
/images/2016-02-29-using-kibana-with-laas/indice.png:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/ovhlabs/knowledge-base/b6339a6f5d858fcee972f4c4a451870bf7464d26/images/2016-02-29-using-kibana-with-laas/indice.png


--------------------------------------------------------------------------------
/images/2016-02-29-using-kibana-with-laas/kibana.png:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/ovhlabs/knowledge-base/b6339a6f5d858fcee972f4c4a451870bf7464d26/images/2016-02-29-using-kibana-with-laas/kibana.png


--------------------------------------------------------------------------------
/images/2016-03-08-quick-start/EnableKibana.png:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/ovhlabs/knowledge-base/b6339a6f5d858fcee972f4c4a451870bf7464d26/images/2016-03-08-quick-start/EnableKibana.png


--------------------------------------------------------------------------------
/images/2016-03-08-quick-start/button.png:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/ovhlabs/knowledge-base/b6339a6f5d858fcee972f4c4a451870bf7464d26/images/2016-03-08-quick-start/button.png


--------------------------------------------------------------------------------
/images/2016-03-08-quick-start/critical-dashboard-2.png:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/ovhlabs/knowledge-base/b6339a6f5d858fcee972f4c4a451870bf7464d26/images/2016-03-08-quick-start/critical-dashboard-2.png


--------------------------------------------------------------------------------
/images/2016-03-08-quick-start/critical-dashboard.png:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/ovhlabs/knowledge-base/b6339a6f5d858fcee972f4c4a451870bf7464d26/images/2016-03-08-quick-start/critical-dashboard.png


--------------------------------------------------------------------------------
/images/2016-03-08-quick-start/editDashboard.png:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/ovhlabs/knowledge-base/b6339a6f5d858fcee972f4c4a451870bf7464d26/images/2016-03-08-quick-start/editDashboard.png


--------------------------------------------------------------------------------
/images/2016-03-08-quick-start/editRole.png:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/ovhlabs/knowledge-base/b6339a6f5d858fcee972f4c4a451870bf7464d26/images/2016-03-08-quick-start/editRole.png


--------------------------------------------------------------------------------
/images/2016-03-08-quick-start/editStream.png:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/ovhlabs/knowledge-base/b6339a6f5d858fcee972f4c4a451870bf7464d26/images/2016-03-08-quick-start/editStream.png


--------------------------------------------------------------------------------
/images/2016-03-08-quick-start/graylog-stream.png:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/ovhlabs/knowledge-base/b6339a6f5d858fcee972f4c4a451870bf7464d26/images/2016-03-08-quick-start/graylog-stream.png


--------------------------------------------------------------------------------
/images/2016-03-08-quick-start/inputs-ports.png:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/ovhlabs/knowledge-base/b6339a6f5d858fcee972f4c4a451870bf7464d26/images/2016-03-08-quick-start/inputs-ports.png


--------------------------------------------------------------------------------
/images/2016-03-08-quick-start/kibanaCreated.png:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/ovhlabs/knowledge-base/b6339a6f5d858fcee972f4c4a451870bf7464d26/images/2016-03-08-quick-start/kibanaCreated.png


--------------------------------------------------------------------------------
/images/2016-03-08-quick-start/login.png:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/ovhlabs/knowledge-base/b6339a6f5d858fcee972f4c4a451870bf7464d26/images/2016-03-08-quick-start/login.png


--------------------------------------------------------------------------------
/images/2016-03-08-quick-start/manager.png:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/ovhlabs/knowledge-base/b6339a6f5d858fcee972f4c4a451870bf7464d26/images/2016-03-08-quick-start/manager.png


--------------------------------------------------------------------------------
/images/2016-03-08-quick-start/manager_start.png:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/ovhlabs/knowledge-base/b6339a6f5d858fcee972f4c4a451870bf7464d26/images/2016-03-08-quick-start/manager_start.png


--------------------------------------------------------------------------------
/images/2016-03-08-quick-start/newAlert.png:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/ovhlabs/knowledge-base/b6339a6f5d858fcee972f4c4a451870bf7464d26/images/2016-03-08-quick-start/newAlert.png


--------------------------------------------------------------------------------
/images/2016-03-08-quick-start/newAlias.png:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/ovhlabs/knowledge-base/b6339a6f5d858fcee972f4c4a451870bf7464d26/images/2016-03-08-quick-start/newAlias.png


--------------------------------------------------------------------------------
/images/2016-03-08-quick-start/newDashboard.png:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/ovhlabs/knowledge-base/b6339a6f5d858fcee972f4c4a451870bf7464d26/images/2016-03-08-quick-start/newDashboard.png


--------------------------------------------------------------------------------
/images/2016-03-08-quick-start/newDashboard_2.png:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/ovhlabs/knowledge-base/b6339a6f5d858fcee972f4c4a451870bf7464d26/images/2016-03-08-quick-start/newDashboard_2.png


--------------------------------------------------------------------------------
/images/2016-03-08-quick-start/newRole.png:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/ovhlabs/knowledge-base/b6339a6f5d858fcee972f4c4a451870bf7464d26/images/2016-03-08-quick-start/newRole.png


--------------------------------------------------------------------------------
/images/2016-03-08-quick-start/newRole_2.png:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/ovhlabs/knowledge-base/b6339a6f5d858fcee972f4c4a451870bf7464d26/images/2016-03-08-quick-start/newRole_2.png


--------------------------------------------------------------------------------
/images/2016-03-08-quick-start/newStream.png:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/ovhlabs/knowledge-base/b6339a6f5d858fcee972f4c4a451870bf7464d26/images/2016-03-08-quick-start/newStream.png


--------------------------------------------------------------------------------
/images/2016-03-08-quick-start/newStream_2.png:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/ovhlabs/knowledge-base/b6339a6f5d858fcee972f4c4a451870bf7464d26/images/2016-03-08-quick-start/newStream_2.png


--------------------------------------------------------------------------------
/images/2016-03-08-quick-start/quick-values.png:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/ovhlabs/knowledge-base/b6339a6f5d858fcee972f4c4a451870bf7464d26/images/2016-03-08-quick-start/quick-values.png


--------------------------------------------------------------------------------
/images/2016-03-08-quick-start/roleAcl.png:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/ovhlabs/knowledge-base/b6339a6f5d858fcee972f4c4a451870bf7464d26/images/2016-03-08-quick-start/roleAcl.png


--------------------------------------------------------------------------------
/images/2016-03-08-quick-start/roleMembers.png:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/ovhlabs/knowledge-base/b6339a6f5d858fcee972f4c4a451870bf7464d26/images/2016-03-08-quick-start/roleMembers.png


--------------------------------------------------------------------------------
/images/2016-03-08-quick-start/start.png:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/ovhlabs/knowledge-base/b6339a6f5d858fcee972f4c4a451870bf7464d26/images/2016-03-08-quick-start/start.png


--------------------------------------------------------------------------------
/images/2016-04-20-marathon-health-checks/health_check.png:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/ovhlabs/knowledge-base/b6339a6f5d858fcee972f4c4a451870bf7464d26/images/2016-04-20-marathon-health-checks/health_check.png


--------------------------------------------------------------------------------
/images/2016-04-20-quick-start-with-marathon/create_container_1.png:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/ovhlabs/knowledge-base/b6339a6f5d858fcee972f4c4a451870bf7464d26/images/2016-04-20-quick-start-with-marathon/create_container_1.png


--------------------------------------------------------------------------------
/images/2016-04-20-quick-start-with-marathon/create_container_2.png:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/ovhlabs/knowledge-base/b6339a6f5d858fcee972f4c4a451870bf7464d26/images/2016-04-20-quick-start-with-marathon/create_container_2.png


--------------------------------------------------------------------------------
/images/2016-04-20-quick-start-with-marathon/create_container_3.png:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/ovhlabs/knowledge-base/b6339a6f5d858fcee972f4c4a451870bf7464d26/images/2016-04-20-quick-start-with-marathon/create_container_3.png


--------------------------------------------------------------------------------
/images/2016-04-20-quick-start-with-marathon/create_container_4.png:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/ovhlabs/knowledge-base/b6339a6f5d858fcee972f4c4a451870bf7464d26/images/2016-04-20-quick-start-with-marathon/create_container_4.png


--------------------------------------------------------------------------------
/images/2016-04-20-quick-start-with-marathon/marathon.png:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/ovhlabs/knowledge-base/b6339a6f5d858fcee972f4c4a451870bf7464d26/images/2016-04-20-quick-start-with-marathon/marathon.png


--------------------------------------------------------------------------------
/images/2016-04-21-marathon-load-balancer/architecture.png:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/ovhlabs/knowledge-base/b6339a6f5d858fcee972f4c4a451870bf7464d26/images/2016-04-21-marathon-load-balancer/architecture.png


--------------------------------------------------------------------------------
/images/2016-04-21-marathon-load-balancer/haproxy.png:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/ovhlabs/knowledge-base/b6339a6f5d858fcee972f4c4a451870bf7464d26/images/2016-04-21-marathon-load-balancer/haproxy.png


--------------------------------------------------------------------------------
/images/2016-04-21-marathon-logs/about.png:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/ovhlabs/knowledge-base/b6339a6f5d858fcee972f4c4a451870bf7464d26/images/2016-04-21-marathon-logs/about.png


--------------------------------------------------------------------------------
/images/2016-04-21-marathon-logs/labels.png:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/ovhlabs/knowledge-base/b6339a6f5d858fcee972f4c4a451870bf7464d26/images/2016-04-21-marathon-logs/labels.png


--------------------------------------------------------------------------------
/images/2016-04-21-marathon-logs/token.png:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/ovhlabs/knowledge-base/b6339a6f5d858fcee972f4c4a451870bf7464d26/images/2016-04-21-marathon-logs/token.png


--------------------------------------------------------------------------------
/images/2016-04-21-marathon-metrics/metrics.png:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/ovhlabs/knowledge-base/b6339a6f5d858fcee972f4c4a451870bf7464d26/images/2016-04-21-marathon-metrics/metrics.png


--------------------------------------------------------------------------------
/images/2016-04-21-marathon-metrics/metrics_cpu.png:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/ovhlabs/knowledge-base/b6339a6f5d858fcee972f4c4a451870bf7464d26/images/2016-04-21-marathon-metrics/metrics_cpu.png


--------------------------------------------------------------------------------
/images/2016-05-03-how-to-use-deskaas-lab/offers.png:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/ovhlabs/knowledge-base/b6339a6f5d858fcee972f4c4a451870bf7464d26/images/2016-05-03-how-to-use-deskaas-lab/offers.png


--------------------------------------------------------------------------------
/images/2016-05-03-how-to-use-deskaas-lab/orderfrommanager.png:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/ovhlabs/knowledge-base/b6339a6f5d858fcee972f4c4a451870bf7464d26/images/2016-05-03-how-to-use-deskaas-lab/orderfrommanager.png


--------------------------------------------------------------------------------
/images/2016-05-03-how-to-use-deskaas-lab/soft_authentication.png:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/ovhlabs/knowledge-base/b6339a6f5d858fcee972f4c4a451870bf7464d26/images/2016-05-03-how-to-use-deskaas-lab/soft_authentication.png


--------------------------------------------------------------------------------
/images/2016-05-03-how-to-use-deskaas-lab/soft_list-desktops.png:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/ovhlabs/knowledge-base/b6339a6f5d858fcee972f4c4a451870bf7464d26/images/2016-05-03-how-to-use-deskaas-lab/soft_list-desktops.png


--------------------------------------------------------------------------------
/images/2016-05-03-how-to-use-deskaas-lab/soft_lists-servers.png:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/ovhlabs/knowledge-base/b6339a6f5d858fcee972f4c4a451870bf7464d26/images/2016-05-03-how-to-use-deskaas-lab/soft_lists-servers.png


--------------------------------------------------------------------------------
/images/2016-05-03-how-to-use-deskaas-lab/soft_logged-in.png:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/ovhlabs/knowledge-base/b6339a6f5d858fcee972f4c4a451870bf7464d26/images/2016-05-03-how-to-use-deskaas-lab/soft_logged-in.png


--------------------------------------------------------------------------------
/images/2016-05-03-how-to-use-deskaas-lab/soft_new-server.png:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/ovhlabs/knowledge-base/b6339a6f5d858fcee972f4c4a451870bf7464d26/images/2016-05-03-how-to-use-deskaas-lab/soft_new-server.png


--------------------------------------------------------------------------------
/images/2016-05-03-how-to-use-deskaas-lab/web_client_desktop.png:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/ovhlabs/knowledge-base/b6339a6f5d858fcee972f4c4a451870bf7464d26/images/2016-05-03-how-to-use-deskaas-lab/web_client_desktop.png


--------------------------------------------------------------------------------
/images/2016-05-03-how-to-use-deskaas-lab/web_client_launchitems.png:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/ovhlabs/knowledge-base/b6339a6f5d858fcee972f4c4a451870bf7464d26/images/2016-05-03-how-to-use-deskaas-lab/web_client_launchitems.png


--------------------------------------------------------------------------------
/images/2016-05-03-how-to-use-deskaas-lab/web_client_login.png:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/ovhlabs/knowledge-base/b6339a6f5d858fcee972f4c4a451870bf7464d26/images/2016-05-03-how-to-use-deskaas-lab/web_client_login.png


--------------------------------------------------------------------------------
/images/2016-05-03-how-to-use-deskaas-lab/web_client_menu.png:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/ovhlabs/knowledge-base/b6339a6f5d858fcee972f4c4a451870bf7464d26/images/2016-05-03-how-to-use-deskaas-lab/web_client_menu.png


--------------------------------------------------------------------------------
/images/2016-05-03-how-to-use-deskaas-lab/web_client_welcome.png:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/ovhlabs/knowledge-base/b6339a6f5d858fcee972f4c4a451870bf7464d26/images/2016-05-03-how-to-use-deskaas-lab/web_client_welcome.png


--------------------------------------------------------------------------------
/images/2016-06-15-getting-started-with-queue-as-a-service/default_users_credentials.png:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/ovhlabs/knowledge-base/b6339a6f5d858fcee972f4c4a451870bf7464d26/images/2016-06-15-getting-started-with-queue-as-a-service/default_users_credentials.png


--------------------------------------------------------------------------------
/images/2016-06-15-getting-started-with-queue-as-a-service/queue_description.png:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/ovhlabs/knowledge-base/b6339a6f5d858fcee972f4c4a451870bf7464d26/images/2016-06-15-getting-started-with-queue-as-a-service/queue_description.png


--------------------------------------------------------------------------------
/images/2016-06-15-getting-started-with-queue-as-a-service/queue_info.png:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/ovhlabs/knowledge-base/b6339a6f5d858fcee972f4c4a451870bf7464d26/images/2016-06-15-getting-started-with-queue-as-a-service/queue_info.png


--------------------------------------------------------------------------------
/images/2016-06-15-getting-started-with-queue-as-a-service/queue_not_configured_app.png:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/ovhlabs/knowledge-base/b6339a6f5d858fcee972f4c4a451870bf7464d26/images/2016-06-15-getting-started-with-queue-as-a-service/queue_not_configured_app.png


--------------------------------------------------------------------------------
/images/2016-06-15-getting-started-with-queue-as-a-service/queue_not_configured_app_menu.png:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/ovhlabs/knowledge-base/b6339a6f5d858fcee972f4c4a451870bf7464d26/images/2016-06-15-getting-started-with-queue-as-a-service/queue_not_configured_app_menu.png


--------------------------------------------------------------------------------
/images/2016-06-15-getting-started-with-queue-as-a-service/queue_sunrise.png:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/ovhlabs/knowledge-base/b6339a6f5d858fcee972f4c4a451870bf7464d26/images/2016-06-15-getting-started-with-queue-as-a-service/queue_sunrise.png


--------------------------------------------------------------------------------
/images/2016-06-17-marathon-api-worker-queue/api.png:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/ovhlabs/knowledge-base/b6339a6f5d858fcee972f4c4a451870bf7464d26/images/2016-06-17-marathon-api-worker-queue/api.png


--------------------------------------------------------------------------------
/images/2016-06-17-marathon-api-worker-queue/api2.png:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/ovhlabs/knowledge-base/b6339a6f5d858fcee972f4c4a451870bf7464d26/images/2016-06-17-marathon-api-worker-queue/api2.png


--------------------------------------------------------------------------------
/images/2016-06-17-marathon-api-worker-queue/design.png:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/ovhlabs/knowledge-base/b6339a6f5d858fcee972f4c4a451870bf7464d26/images/2016-06-17-marathon-api-worker-queue/design.png


--------------------------------------------------------------------------------
/images/2016-06-17-marathon-api-worker-queue/redis.png:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/ovhlabs/knowledge-base/b6339a6f5d858fcee972f4c4a451870bf7464d26/images/2016-06-17-marathon-api-worker-queue/redis.png


--------------------------------------------------------------------------------
/images/2016-06-17-marathon-api-worker-queue/redis2.png:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/ovhlabs/knowledge-base/b6339a6f5d858fcee972f4c4a451870bf7464d26/images/2016-06-17-marathon-api-worker-queue/redis2.png


--------------------------------------------------------------------------------
/images/2016-06-17-marathon-api-worker-queue/redis3.png:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/ovhlabs/knowledge-base/b6339a6f5d858fcee972f4c4a451870bf7464d26/images/2016-06-17-marathon-api-worker-queue/redis3.png


--------------------------------------------------------------------------------
/images/2016-06-17-marathon-api-worker-queue/worker.png:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/ovhlabs/knowledge-base/b6339a6f5d858fcee972f4c4a451870bf7464d26/images/2016-06-17-marathon-api-worker-queue/worker.png


--------------------------------------------------------------------------------
/images/2016-06-21-deploying-wordpress-on-marathon/phpmyadmin-welcome.png:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/ovhlabs/knowledge-base/b6339a6f5d858fcee972f4c4a451870bf7464d26/images/2016-06-21-deploying-wordpress-on-marathon/phpmyadmin-welcome.png


--------------------------------------------------------------------------------
/images/2016-06-21-deploying-wordpress-on-marathon/phpmyadmin.png:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/ovhlabs/knowledge-base/b6339a6f5d858fcee972f4c4a451870bf7464d26/images/2016-06-21-deploying-wordpress-on-marathon/phpmyadmin.png


--------------------------------------------------------------------------------
/images/2016-06-21-deploying-wordpress-on-marathon/phpmyadmin2.png:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/ovhlabs/knowledge-base/b6339a6f5d858fcee972f4c4a451870bf7464d26/images/2016-06-21-deploying-wordpress-on-marathon/phpmyadmin2.png


--------------------------------------------------------------------------------
/images/2016-06-21-deploying-wordpress-on-marathon/whitelist.png:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/ovhlabs/knowledge-base/b6339a6f5d858fcee972f4c4a451870bf7464d26/images/2016-06-21-deploying-wordpress-on-marathon/whitelist.png


--------------------------------------------------------------------------------
/images/2016-06-21-deploying-wordpress-on-marathon/wordpress-welcome.png:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/ovhlabs/knowledge-base/b6339a6f5d858fcee972f4c4a451870bf7464d26/images/2016-06-21-deploying-wordpress-on-marathon/wordpress-welcome.png


--------------------------------------------------------------------------------
/images/2016-06-21-deploying-wordpress-on-marathon/wordpress.png:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/ovhlabs/knowledge-base/b6339a6f5d858fcee972f4c4a451870bf7464d26/images/2016-06-21-deploying-wordpress-on-marathon/wordpress.png


--------------------------------------------------------------------------------
/images/2016-06-21-deploying-wordpress-on-marathon/wordpress2.png:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/ovhlabs/knowledge-base/b6339a6f5d858fcee972f4c4a451870bf7464d26/images/2016-06-21-deploying-wordpress-on-marathon/wordpress2.png


--------------------------------------------------------------------------------
/images/2016-06-23-linux-and-skylake/distrib_kernel.png:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/ovhlabs/knowledge-base/b6339a6f5d858fcee972f4c4a451870bf7464d26/images/2016-06-23-linux-and-skylake/distrib_kernel.png


--------------------------------------------------------------------------------
/images/2016-06-23-linux-and-skylake/rescue1.png:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/ovhlabs/knowledge-base/b6339a6f5d858fcee972f4c4a451870bf7464d26/images/2016-06-23-linux-and-skylake/rescue1.png


--------------------------------------------------------------------------------
/images/2016-06-23-linux-and-skylake/rescue2.png:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/ovhlabs/knowledge-base/b6339a6f5d858fcee972f4c4a451870bf7464d26/images/2016-06-23-linux-and-skylake/rescue2.png


--------------------------------------------------------------------------------
/images/2016-07-25-kafka-topics-management/sunrise-topics.png:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/ovhlabs/knowledge-base/b6339a6f5d858fcee972f4c4a451870bf7464d26/images/2016-07-25-kafka-topics-management/sunrise-topics.png


--------------------------------------------------------------------------------
/images/2016-08-17-dbaas-queue-https/sunrise-info.png:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/ovhlabs/knowledge-base/b6339a6f5d858fcee972f4c4a451870bf7464d26/images/2016-08-17-dbaas-queue-https/sunrise-info.png


--------------------------------------------------------------------------------
/images/2016-10-24-kafka-sasl-ssl/sunrise-roles.png:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/ovhlabs/knowledge-base/b6339a6f5d858fcee972f4c4a451870bf7464d26/images/2016-10-24-kafka-sasl-ssl/sunrise-roles.png


--------------------------------------------------------------------------------
/images/2016-10-24-kafka-sasl-ssl/sunrise-users.png:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/ovhlabs/knowledge-base/b6339a6f5d858fcee972f4c4a451870bf7464d26/images/2016-10-24-kafka-sasl-ssl/sunrise-users.png


--------------------------------------------------------------------------------
/images/2016-11-07-using-a-private-registry/private-registry.png:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/ovhlabs/knowledge-base/b6339a6f5d858fcee972f4c4a451870bf7464d26/images/2016-11-07-using-a-private-registry/private-registry.png


--------------------------------------------------------------------------------
/images/2017-01-04-how-to-start-with-your-private-docker-registry/accounts_listing.png:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/ovhlabs/knowledge-base/b6339a6f5d858fcee972f4c4a451870bf7464d26/images/2017-01-04-how-to-start-with-your-private-docker-registry/accounts_listing.png


--------------------------------------------------------------------------------
/images/2017-01-04-how-to-start-with-your-private-docker-registry/images_listing.png:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/ovhlabs/knowledge-base/b6339a6f5d858fcee972f4c4a451870bf7464d26/images/2017-01-04-how-to-start-with-your-private-docker-registry/images_listing.png


--------------------------------------------------------------------------------
/images/2017-01-04-how-to-start-with-your-private-docker-registry/namespace_creation.png:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/ovhlabs/knowledge-base/b6339a6f5d858fcee972f4c4a451870bf7464d26/images/2017-01-04-how-to-start-with-your-private-docker-registry/namespace_creation.png


--------------------------------------------------------------------------------
/images/2017-01-04-how-to-start-with-your-private-docker-registry/namespace_details.png:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/ovhlabs/knowledge-base/b6339a6f5d858fcee972f4c4a451870bf7464d26/images/2017-01-04-how-to-start-with-your-private-docker-registry/namespace_details.png


--------------------------------------------------------------------------------
/images/2017-01-04-how-to-start-with-your-private-docker-registry/user_creation.png:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/ovhlabs/knowledge-base/b6339a6f5d858fcee972f4c4a451870bf7464d26/images/2017-01-04-how-to-start-with-your-private-docker-registry/user_creation.png


--------------------------------------------------------------------------------
/images/2017-01-04-how-to-start-with-your-private-docker-registry/user_listing.png:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/ovhlabs/knowledge-base/b6339a6f5d858fcee972f4c4a451870bf7464d26/images/2017-01-04-how-to-start-with-your-private-docker-registry/user_listing.png


--------------------------------------------------------------------------------
/images/2017-01-04-how-to-start-with-your-private-docker-registry/user_permissions_add.png:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/ovhlabs/knowledge-base/b6339a6f5d858fcee972f4c4a451870bf7464d26/images/2017-01-04-how-to-start-with-your-private-docker-registry/user_permissions_add.png


--------------------------------------------------------------------------------
/images/2017-01-31-kafka-metrics-grafana/Screenshot from 2017-01-29 21-41-29.png:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/ovhlabs/knowledge-base/b6339a6f5d858fcee972f4c4a451870bf7464d26/images/2017-01-31-kafka-metrics-grafana/Screenshot from 2017-01-29 21-41-29.png


--------------------------------------------------------------------------------
/images/2017-01-31-kafka-metrics-grafana/applications_list.png:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/ovhlabs/knowledge-base/b6339a6f5d858fcee972f4c4a451870bf7464d26/images/2017-01-31-kafka-metrics-grafana/applications_list.png


--------------------------------------------------------------------------------
/images/2017-01-31-kafka-metrics-grafana/credentials.png:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/ovhlabs/knowledge-base/b6339a6f5d858fcee972f4c4a451870bf7464d26/images/2017-01-31-kafka-metrics-grafana/credentials.png


--------------------------------------------------------------------------------
/images/2017-01-31-kafka-metrics-grafana/data_source.png:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/ovhlabs/knowledge-base/b6339a6f5d858fcee972f4c4a451870bf7464d26/images/2017-01-31-kafka-metrics-grafana/data_source.png


--------------------------------------------------------------------------------
/images/2017-01-31-kafka-metrics-grafana/datasource_configuration.png:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/ovhlabs/knowledge-base/b6339a6f5d858fcee972f4c4a451870bf7464d26/images/2017-01-31-kafka-metrics-grafana/datasource_configuration.png


--------------------------------------------------------------------------------
/images/2017-01-31-kafka-metrics-grafana/graph_with_tag.png:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/ovhlabs/knowledge-base/b6339a6f5d858fcee972f4c4a451870bf7464d26/images/2017-01-31-kafka-metrics-grafana/graph_with_tag.png


--------------------------------------------------------------------------------
/images/2017-01-31-kafka-metrics-grafana/graph_without_tag.png:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/ovhlabs/knowledge-base/b6339a6f5d858fcee972f4c4a451870bf7464d26/images/2017-01-31-kafka-metrics-grafana/graph_without_tag.png


--------------------------------------------------------------------------------
/images/2017-01-31-kafka-metrics-grafana/new_graph.png:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/ovhlabs/knowledge-base/b6339a6f5d858fcee972f4c4a451870bf7464d26/images/2017-01-31-kafka-metrics-grafana/new_graph.png


--------------------------------------------------------------------------------
/images/2017-01-31-kafka-metrics-grafana/new_organization.png:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/ovhlabs/knowledge-base/b6339a6f5d858fcee972f4c4a451870bf7464d26/images/2017-01-31-kafka-metrics-grafana/new_organization.png


--------------------------------------------------------------------------------
/images/2017-01-31-kafka-metrics-grafana/select_datasource.png:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/ovhlabs/knowledge-base/b6339a6f5d858fcee972f4c4a451870bf7464d26/images/2017-01-31-kafka-metrics-grafana/select_datasource.png


--------------------------------------------------------------------------------
/images/author-github.png:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/ovhlabs/knowledge-base/b6339a6f5d858fcee972f4c4a451870bf7464d26/images/author-github.png


--------------------------------------------------------------------------------
/images/community/arrowLink.png:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/ovhlabs/knowledge-base/b6339a6f5d858fcee972f4c4a451870bf7464d26/images/community/arrowLink.png


--------------------------------------------------------------------------------
/images/community/gear.png:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/ovhlabs/knowledge-base/b6339a6f5d858fcee972f4c4a451870bf7464d26/images/community/gear.png


--------------------------------------------------------------------------------
/images/community/user.png:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/ovhlabs/knowledge-base/b6339a6f5d858fcee972f4c4a451870bf7464d26/images/community/user.png


--------------------------------------------------------------------------------
/images/favicon.ico:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/ovhlabs/knowledge-base/b6339a6f5d858fcee972f4c4a451870bf7464d26/images/favicon.ico


--------------------------------------------------------------------------------
/images/github.png:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/ovhlabs/knowledge-base/b6339a6f5d858fcee972f4c4a451870bf7464d26/images/github.png


--------------------------------------------------------------------------------
/images/icon-gitHub-footer.png:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/ovhlabs/knowledge-base/b6339a6f5d858fcee972f4c4a451870bf7464d26/images/icon-gitHub-footer.png


--------------------------------------------------------------------------------
/images/icon-twitter-footer.png:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/ovhlabs/knowledge-base/b6339a6f5d858fcee972f4c4a451870bf7464d26/images/icon-twitter-footer.png


--------------------------------------------------------------------------------
/images/logo-top.png:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/ovhlabs/knowledge-base/b6339a6f5d858fcee972f4c4a451870bf7464d26/images/logo-top.png


--------------------------------------------------------------------------------
/images/twitter.png:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/ovhlabs/knowledge-base/b6339a6f5d858fcee972f4c4a451870bf7464d26/images/twitter.png


--------------------------------------------------------------------------------
/index.html:
--------------------------------------------------------------------------------
1 | ---
2 | layout: home 
3 | lang: en
4 | ---
5 | 
6 | 


--------------------------------------------------------------------------------
/styles/fonts/lato/lato-light-webfont.woff:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/ovhlabs/knowledge-base/b6339a6f5d858fcee972f4c4a451870bf7464d26/styles/fonts/lato/lato-light-webfont.woff


--------------------------------------------------------------------------------
/styles/fonts/lato/lato-regular-webfont.woff:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/ovhlabs/knowledge-base/b6339a6f5d858fcee972f4c4a451870bf7464d26/styles/fonts/lato/lato-regular-webfont.woff


--------------------------------------------------------------------------------
/styles/images/twitter.png:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/ovhlabs/knowledge-base/b6339a6f5d858fcee972f4c4a451870bf7464d26/styles/images/twitter.png


--------------------------------------------------------------------------------
/styles/knowledge-base.css:
--------------------------------------------------------------------------------
 1 | .pagination {
 2 | 	display: inline-block;
 3 | 	text-align: center;
 4 | 	width: 100%;
 5 | 	margin: 20px 0;
 6 | }
 7 | .pagination span, .pagination em, .pagination a {
 8 | 	display: inline-block;
 9 | 	margin-right: 6px;
10 | 	vertical-align: text-bottom;
11 | 	background: none repeat scroll 0% 0% #2E2E2C;
12 | 	color: #7D7979;
13 | 	padding: 5px 2%;
14 | 	font-size: 18px;
15 | 	font-weight: 300;
16 | 	line-height: 24px;
17 | }
18 | .pagination a {
19 | 	color: #FFA51B;
20 | }
21 | .post-content {
22 | 	margin: 30px 0;
23 | }
24 | 
25 | .post-content p {
26 | 	margin: 15px 0;
27 | }
28 | 
29 | .post-content h1 {
30 | 	text-indent: inherit;
31 | 	margin:30px 0 10px 0;
32 |     font-size:34px;
33 |     line-height:40px;
34 |     font-weight: 200;
35 | }
36 | .post-content h2 {
37 | 	margin:30px 0 10px 0;
38 |     font-size:26px;
39 |     line-height:30px;
40 | }
41 | .post-content h3 {
42 |     margin:30px 0 10px 0;
43 |     font-size:18px;
44 |     line-height:24px;
45 | }
46 | .post-content h4 {
47 |     margin:30px 0 10px 0;
48 |     font-size:16px;
49 |     line-height:22px;
50 | }
51 | .post-content pre code {
52 | 	margin: 20px 0 10px 0;
53 | 	display: block;
54 | 	padding: 10px 20px;
55 | 	background-color: rgba(24, 24, 24, 0.1);
56 | }
57 | .post-content code {
58 | 	margin: 20px 0 10px 0;
59 | 	background-color: rgba(24, 24, 24, 0.1);
60 | }
61 | .arian {
62 | 	display: block;
63 | 	width: 100%;
64 | 	margin: 0px 0px 20px;
65 | }
66 | .arian a {
67 | 	font-size: 16px;
68 | 	font-weight: 300;
69 | }
70 | .meta, .meta a {
71 | 	color: #747070;
72 | }
73 | .banner {
74 | 	width: 80%;
75 | 	margin: auto;
76 | 	margin-bottom: 50px;
77 | }
78 | code, .highlight pre code, .highlight pre code span {
79 |     overflow: auto;
80 |     font-family: "Courier" !important;
81 | }
82 | .highlight .bp {
83 |     font-size: 15px !important;
84 | }
85 | .github_icon {
86 | 	width: 14px;
87 | 	height: 14px;
88 | }
89 | 


--------------------------------------------------------------------------------
/styles/responsive-nav.css:
--------------------------------------------------------------------------------
 1 | /*! responsive-nav.js 1.0.32 by @viljamis */
 2 | 
 3 | .nav-collapse ul {
 4 |   margin: 0;
 5 |   padding: 0;
 6 |   width: 100%;
 7 |   display: block;
 8 |   list-style: none;
 9 | }
10 | 
11 | .nav-collapse li {
12 |   display: block;
13 | }
14 | 
15 | .js .nav-collapse {
16 |   clip: rect(0 0 0 0);
17 |   max-height: 0;
18 |   position: absolute;
19 |   display: block;
20 |   overflow: hidden;
21 |   zoom: 1;
22 | }
23 | 
24 | .nav-collapse.opened {
25 |   max-height: 9999px;
26 | }
27 | 
28 | .disable-pointer-events {
29 |   pointer-events: none !important;
30 | }
31 | 
32 | .nav-toggle {
33 |   -webkit-tap-highlight-color: rgba(0,0,0,0);
34 |   -webkit-touch-callout: none;
35 |   -webkit-user-select: none;
36 |   -moz-user-select: none;
37 |   -ms-user-select: none;
38 |   -o-user-select: none;
39 |   user-select: none;
40 | }
41 | 
42 | @media screen and (min-width: 768px) {
43 |   .js .nav-collapse {
44 |     position: relative;
45 |   }
46 |   .js .nav-collapse.closed {
47 |     max-height: none;
48 |   }
49 |   .nav-toggle {
50 |     display: none;
51 |   }
52 | }
53 | 


--------------------------------------------------------------------------------
/styles/styles-nav.css:
--------------------------------------------------------------------------------
  1 | @charset "UTF-8";
  2 | 
  3 | /* ------------------------------------------
  4 |   NAVIGATION STYLES
  5 |   (+ responsive-nav.css file is loaded in the <head>)
  6 | --------------------------------------------- */
  7 | 
  8 | .fixed {
  9 |   position: fixed;
 10 |   width: 100%;
 11 |   top: 0;
 12 |   left: 0;
 13 | }
 14 | 
 15 | 
 16 | @media screen and (max-width: 770px) {
 17 |     .nav-collapse { width : 100%; }
 18 | 
 19 |     .nav-collapse ul.topmenu li {
 20 |         width : 100%;
 21 |         text-align: center;
 22 |         background: #000;
 23 |         border-bottom : 1px solid #FFFFFF;
 24 |     }
 25 | 
 26 |     #header .wrapper ul.topmenu li span {
 27 |         display : block;
 28 |         width: 100%;
 29 |     }
 30 | 
 31 |     #header .wrapper ul.topmenu li a {
 32 |         display : block;
 33 |         height : 100%;
 34 |         padding : 0.7em  1em;
 35 |         width: 100%;
 36 |     }
 37 | 
 38 |     #header .wrapper ul.topmenu li a:hover { background-color : #333; color:#fff;}
 39 | 
 40 |     .nav-collapse ul.topmenu li a {
 41 |         text-align : center;
 42 |         color : #FFFFFF;
 43 |         font-weight : 600;
 44 |     }
 45 | }
 46 | 
 47 | 
 48 | /* ------------------------------------------
 49 |   NAV TOGGLE STYLES
 50 | --------------------------------------------- */
 51 | 
 52 | .nav-toggle {
 53 |   position: fixed;
 54 |   -webkit-font-smoothing: antialiased;
 55 |   -moz-osx-font-smoothing: grayscale;
 56 |   -webkit-touch-callout: none;
 57 |   -webkit-user-select: none;
 58 |   -moz-user-select: none;
 59 |   -ms-user-select: none;
 60 |   user-select: none;
 61 |   text-decoration: none;
 62 |   text-indent: -999px;
 63 |   position: relative;
 64 |   overflow: hidden;
 65 |   width: 70px;
 66 |   height: 55px;
 67 |   float: right;
 68 | }
 69 | 
 70 | .nav-toggle:before {
 71 |   color: #FF980A; /* Edit this to change the icon color */
 72 |   font-family: "responsivenav", sans-serif;
 73 |   font-style: normal;
 74 |   font-weight: normal;
 75 |   font-variant: normal;
 76 |   font-size: 65px;
 77 |   text-transform: none;
 78 |   position: absolute;
 79 |   content: "≡";
 80 |   text-indent: 0;
 81 |   text-align: center;
 82 |   line-height: 70px;
 83 |   speak: none;
 84 |   width: 100%;
 85 |   top: 0;
 86 |   left: 0;
 87 | }
 88 | 
 89 | .nav-toggle.active::before {
 90 |   font-size: 40px;
 91 |   content:"x";
 92 | }
 93 | 
 94 | @media screen and (max-width: 390px) {
 95 |     .nav-toggle:before {
 96 |         font-size: 40px;
 97 |     }
 98 |     .nav-toggle.active::before {
 99 |         font-size: 30px;
100 |     }
101 | }
102 | 
103 | 


--------------------------------------------------------------------------------