2. Because the VMAF server will need to de deployed to bytel, the
question on how NN6 will deliver the firmware is now an actual
question.
In order to not be too specific to TESTTREE, a thinking have been done
in order to see how server may be install or upgraded by using generic
and common way to proceed.
GOAL / INTRODUCTION
2
6. The VMAF appliance should not be specific to testtree bu must be
usable by any project
That’s why the vmaf appliance has been designed with standard
interfaces :
A standard REST API for commands/ input request
A common message broker (rabbitMQ) for responses
GOAL
6
13. A customer :
View all of his devices with their version and licence
View all release in relation of the devices
Can synchronise upgrade items with the cutomer upgrade appliance
Can download upgrade items within a pgp encrypted archive
Can launch an upgrade process from the main ui to the customer’s site
NN6 team :
View all device with their current release
Locate all customer on a worldmap
Investigate on equipment using encrypted vpn (over a ssl tummel)
REQUIREMENTS
13
16. Streamprobe
Baremetal
Native BIOS : boot from usb key generated from the img
Idrack (DELL) : using the img key
Ipmi (SUPERMICRO) : boot from usb key generated from the img
VMWARE ESXI
Ova image
Mediacast
Baremetal (supermicro)
VMWARE ESXI
Boot from an ISO image then launch an installer that register RPMS
Inventory of the way to install (1/2)
16
17. Smartgate vt / vt2
Baremetal :
Boot from ISO image then install docker (docker swarm orchestrator)
VMWARE ESXI
Boot from ISO image then install packages
eBox (medicast Mobile + lte gcsas server)
Fedora image install manually then install qemu images (gcow2)
Inventory of the way to install (2/2)
17
18. Which ALMA release V8 or v9 ?
Using an ISO image burn on an USB key, or directly the ISO image
(http://mirror.almalinux.ikoula.com/9.2/isos/x86_64/)
Compatible with:
VMWARE ESXI
BAREMETAL
IDRACK (DELL)
IPMI (SUPERMICRO)
ALMA
18
19. May use ALMA linux but we require ALPINE as possible
Does not need any base install
HELM/CHARTs is the best deployment method to push docker
container and/or services
K8S
19
21. A customer may :
Have several location with UPGRADE APPLIANCE
Inventory all local appliance (by type/release)
Thus, upgrade may control several point through MQTT connexion
Requrements
21
22. 22
SECURED
NETWORK
DMZ
INTERNET
NN6 NETWORK
DOCKER REGISTRY
(CUSTOMER)
UPGRADE BACKEND
• HELM / CHART
• PROVISIONNING (ANSIBLE,
SALT STACK, … )
• …
….
manual
deploy
DOCKER REGISTRY
(PROD)
MQTT broker
MQTT
CLIENT
registry
monitoring
Manual/auto
docker sync
Docker
push
(subscribe)
(publish)
https://mqtt.enensys.com
dockerregistry.enensys.com
CUSTOMER NETWORK
BACKEND
NOSQL DB
https://dashboard.enensys.com
MQTT CLIENT
PACKAGE REGISTRY
(PROD)
DOCKER REGISTRY
(CUSTOMER)
Package
push
packerregistry.enensys.com
LOCAL
GUI
LICENCE REGISTRY
lm.enensys.com LICENCE
CUSTOMER)
FRONTEND / GUI
UPGRADE
APPLIANCE
Licence
push
Architecture based on an ALMA OS
Architecture based on an ALMA OS
ALMA OS