ELIOT IoT Gateway Blueprint
Project Technical Lead: Khemendra Kumar. Elected 1/17/19.
Committer | Committer Company | Committer Contact Info | Committer Bio | Committer Picture | Self Nominate for PTL (Y/N) |
Khemendra Kumar | Huawei |
|
| Y | |
Yang (Gabriel) Yu | Huawei |
|
|
| |
Tianwei Wu | Huawei |
|
|
| |
Maxim Uvarov | Linaro |
|
|
| |
Peng Liu | China Mobile |
|
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
Contributor:
Abhijit Dasgupta (abhijit.das.gupta@huawei.com)
Srinivasan S N (srinivasan.s.n@huawei.com)
ELIOT IoT Gateway Blueprint
Case Attributes | Description | Informational |
Type | New |
|
Blueprint Family - Proposed Name | ELIOT |
|
Use Case | IoT gateway |
|
Blueprint proposed Name | ELIOT IoT gateway |
|
Initial POD Cost (capex) | 100's USD or less As low as $30 |
|
Scale & Type | 10K, 100K, 1000K ARM devices or servers X86 devices or servers |
|
Applications | Smart cities, IIoT, uCPE, ... |
|
Power Restrictions | NA |
|
Infrastructure orchestration | Containers, Kubernetes, Kubernetes ecosystem |
|
SDN | various, or NA |
|
Workload Type | Containers |
|
Additional Details | NA |
|
Comments
Hi Pavan,
Thanks for your effort and appreciate the work done.
sure you can share the changes and qcow2 images and we can discuss based on them. Will followup over the mail.
We have weekly call every Wednesday @6:30 PM IST and we can discuss more about this in that call.
Hi Pavan, can you please point me into the link where your generated documentation is being hosted for this ELIOT Blueprint? Thanks in advance.
Using Kubernetes:
https://docs.google.com/document/d/1TwtDRvxJ_0IFzc5KvO7aaOh3If-jhpCSrccjttQA4LE/edit?usp=sharing
Using KubeEdge:
https://docs.google.com/document/d/1kmSJtX3jZRLJEcHlBSSiwNGDdQ9XVB3xIfEUaeHnWGo/edit?usp=sharing
Let me know if you need anything other information.
Hi,
Our team at Calsoft Inc. has managed to run the ELIOT blueprint with K8s using 2VMS: iot-mgr and iot-node. If it is fine, we can share the qcow2 images of both the VMs which will have the prerequisites and couple of changes required in the VM. People can then simply run the setup.sh file to do the deployment. It will save debug time for people. Also, we will provide the documentation. Let me know if this sounds fine.