Replies: 2 comments
-
|
@akiskourtis @mchristopoulou we can enhance the list of features and decide on the next steps especially for support of OASEES, PRIVATEER |
Beta Was this translation helpful? Give feedback.
-
|
according to this https://osm.etsi.org/docs/user-guide/latest/05-osm-usage.html#using-kubernetes-based-vnfs-knfs OSM expects a preinstalled K8S environment similarly to Openstack. However it can be just a cluster on another Virtualisation Host (e.g. proxmox, openstak, bare metal etc) For OSM you can use one of these three different ways to install your Kubernetes cluster: OSM Kubernetes cluster Network Service The someone can deploy available packets in K8S directly via OSM as part of extended services along with VNFs and PNFs @OikonomakisAndreas we may need your help on this one. We need to have at least a small vanilla Proxmox based K8s in order to test this out. NOTE: Subscription and Notification support in OSM Since the current support is only restricted to NS, while NSD and VNFD are in roadmap, for here onwards we will refer subscription and notification for NS. ` |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
There is clear objective for the Lab to continue the development and the evolution of KATANA Slice Manager. @TheReaperGR has been all over it taking his best shot in revival of KATANA to bring it up to speed with the rest components such as VIM (Latest Openstack) and Orchestrator (OSM).
Currently KATANA is operational for what essentially was the latest set of features before staying behind.
The next steps not with prioritisation are:
Beta Was this translation helpful? Give feedback.
All reactions