ROS Japan UG #34 LT大会 で飛び込みLTした資料です.
https://rosjp.connpass.com/event/161041/
ROS 2のDashing/Eloquentで QoS (Quality of Service) 周りのAPIがそれぞれ破壊的に更新されててツラかったので,そのTIPS・知見を共有させていただきました.
ROS Japan UG #34 LT大会 で飛び込みLTした資料です.
https://rosjp.connpass.com/event/161041/
ROS 2のDashing/Eloquentで QoS (Quality of Service) 周りのAPIがそれぞれ破壊的に更新されててツラかったので,そのTIPS・知見を共有させていただきました.
Literate Computing for Infrastructure - インフラ・コード化の実践におけるIPython (Jupyter) Not...No Bu
Presented at SC2015-6 on 6/3/2015 for ..
Infrastructure as Code meets IPython Notebook to be Literate Computing
IEICE Tech. Rep., vol. 115, no. 72, SC2015-6, pp. 27-32, June 2015.
Abstract: Cloud has put the pressure to rapidly build systems and frequently re-configure services, then Infrastructure as Code has come beyond the simple automation. The approach treats the configuration of systems the same way that software source code is treated. Infrastructure is validated and processed “as Code” with management tools. However, as Code is not limited only about the intelligent automation, but also about the communication based on code for reviewing, reproducing, customizing, and reusing. It is as important to be able to share information and processes with others, as to actually automate complex operations for infrastructures. IPython Notebook is a useful tool to both describe automated operations with code (and configuration data) and share predicted and reproducible outcomes with others, technical and non-technical alike.
IPython Notebook is a “literate computing” tool, which enables us to share stories about infrastructure’s design and elaborated workflows. We will share our experience how the literate stories are also useful for various customer communications as tracing individual issue, promoting self-administration etc.
Keywords DevOps, Infrastructure as Code, Literate Computing, IPython Notebook, Jupyter
インフラ・コード化の実践におけるIPython Notebookの適用
信学技報, vol. 115, no. 72, SC2015-6, pp. 27-32, 2015年6月
あらまし: クラウドサービスの浸透により,サービスの構築・再構築の機会が増加するのに伴って,作業手順をすべてCodeとして記述するInfrastructures as Codeというアプローチが着目されている.ここでの“as Code”は作業手順の正当性がプログラムコードのように,また実行結果も機械的に検証可能であるという意味合いで捉えられがちであるが,むしろ個々の作業の再現性を保証し,その上で作業をカスタマイズ・再利用すると言ったプロセス自体を,Codeとして見える化し,伝達可能にすることにこそ意義がある.DevOpsに於いては,何某かを実際に構築したり機械化したりするだけではなく,設計情報,運用状態を伝達・共有できるようにすることが重要である.
“Literate Computing”ツールと呼ばれ,ワークフローと実行結果を一体としてドキュメント化できるIPython Notebookを,基盤の構築,運用に適用する方式を提案すると共に,具体的な適用によってワークフローをどのように改善することができたかを報告する.
キーワード DevOps, Infrastructure as Code, Literate Computing, IPython Notebook, Jupyter
Literate Computing for Infrastructure - インフラ・コード化の実践におけるIPython (Jupyter) Not...No Bu
Presented at SC2015-6 on 6/3/2015 for ..
Infrastructure as Code meets IPython Notebook to be Literate Computing
IEICE Tech. Rep., vol. 115, no. 72, SC2015-6, pp. 27-32, June 2015.
Abstract: Cloud has put the pressure to rapidly build systems and frequently re-configure services, then Infrastructure as Code has come beyond the simple automation. The approach treats the configuration of systems the same way that software source code is treated. Infrastructure is validated and processed “as Code” with management tools. However, as Code is not limited only about the intelligent automation, but also about the communication based on code for reviewing, reproducing, customizing, and reusing. It is as important to be able to share information and processes with others, as to actually automate complex operations for infrastructures. IPython Notebook is a useful tool to both describe automated operations with code (and configuration data) and share predicted and reproducible outcomes with others, technical and non-technical alike.
IPython Notebook is a “literate computing” tool, which enables us to share stories about infrastructure’s design and elaborated workflows. We will share our experience how the literate stories are also useful for various customer communications as tracing individual issue, promoting self-administration etc.
Keywords DevOps, Infrastructure as Code, Literate Computing, IPython Notebook, Jupyter
インフラ・コード化の実践におけるIPython Notebookの適用
信学技報, vol. 115, no. 72, SC2015-6, pp. 27-32, 2015年6月
あらまし: クラウドサービスの浸透により,サービスの構築・再構築の機会が増加するのに伴って,作業手順をすべてCodeとして記述するInfrastructures as Codeというアプローチが着目されている.ここでの“as Code”は作業手順の正当性がプログラムコードのように,また実行結果も機械的に検証可能であるという意味合いで捉えられがちであるが,むしろ個々の作業の再現性を保証し,その上で作業をカスタマイズ・再利用すると言ったプロセス自体を,Codeとして見える化し,伝達可能にすることにこそ意義がある.DevOpsに於いては,何某かを実際に構築したり機械化したりするだけではなく,設計情報,運用状態を伝達・共有できるようにすることが重要である.
“Literate Computing”ツールと呼ばれ,ワークフローと実行結果を一体としてドキュメント化できるIPython Notebookを,基盤の構築,運用に適用する方式を提案すると共に,具体的な適用によってワークフローをどのように改善することができたかを報告する.
キーワード DevOps, Infrastructure as Code, Literate Computing, IPython Notebook, Jupyter
FIWARE Lab, a service platform based on a large distributed OpenStack environ...FIWARE
'FIWARE Lab, a service platform based on a large distributed OpenStack environment'.
Presentation (in Japanese) by Stefano De Panfilis, FIWARE Foundation COO.
Shown at the OpenStack Days in Tokyo (20/07/2017)
Rclex: A Library for Robotics meet ElixirHideki Takase
Presentation at Code BEAM America 2021
https://codesync.global/conferences/code-beam-sf-2021
https://codesync.global/speaker/hideki-takase/
How do we install the magic of Elixir into robot systems? One of the solutions is "Rclex", that is a client library for ROS 2 platform. ROS (Robot Operating System) provides publish/subscribe based messaging mechanism between robot modules with the DDS (Data Distribution Service) stack. We suggest that the force of Erlang/Elixir can power up the scalability of ROS 2 communication. This talk will introduce how did we integrate ROS 2 and Elixir by using NIFs, and discuss the possibility of this library in the IoT field.
10. takasehideki/EEloT
Raspberry Pi 3 Model B
使いやすさが自慢のIoT時代の風雲児!!
• 4-Core 1.2GHz Cortex-A53 (64bit)
− Broadcom BCM2837
• 1GB LPDDR2 RAM
• BCM43438 WLAN & BLE on board
• Raspbian sketch with Desktop 4.9
− Raspbian GNU/Linux 9 n l
• Ubuntu MATE 16.04
− Ubuntu 16.04.2 LTS n l
10