One of the things we have seen in many catalysts is automation delivered by autonomic managers each optimising within a given scope often using closed control loops.
If you look at M/s Azure that provides services where you state what you need and they provide it . However you can also monitor more or less everything internally. What you are asking for is to be a tenant on their services with a defined capacity and QoS /SLA. Clearly they have to manage the workload requests of many tenants which obviously cannot be done by one tenant alone.
The resistance to automation probably comes about because of a concern about lack of control which arises from several sources
- lack of familiarity with the operational practice of cloud native applications
- and organisation model that emphasises vertical product/ service responsibilities rather than cloud Platforms
Given the volume and velocity of change that occurs with virtualisation it seems inevitable that direct manual control will be imposible ( similar to fly by wire in aircraft where the pilot sets the goals: climb, descend turn etc., but is not actually directly controlling surfaces or engines) .
these points and M/s ( also AWS ) approach also suggests that operations will need to organised horizontally around roughly IaaS, PaaS and SaaS. where the workloads of each layer/platform are managed by a organisation each responsible for managing workload demands on each cloud layer and supported by OSS/IT tools that help them carry out the full lifecycle of that responsibility planning development operation's etc.
------------------------------
Dave Milham
TM Forum Chief Architect
------------------------------
Original Message:
Sent: 02-09-2017 06:13
From: Paul Jordan
Subject: properties of an OSS system
I agree with 1. Real time but my numbers 2 and 3 are different. I'm less concerned about standardisation as I think I can develop enough adaptors to cope with relatively few chosen vendors. I'm currently see resistance to too much automation so prefer the flexibility of policy control over actions and scope. Hence my other two are
2. Data Driven flexibility
3. Policy control over provision and restoration actions
------------------------------
Paul Jordan
BT Group plc
My views may not reflect those of BT
------------------------------
Original Message:
Sent: 02-08-2017 01:48
From: Lalitagauri Dixit
Subject: properties of an OSS system
Hi Johan,
In my opinion, three top most important properties/feature OSS should have are
1. Real time - With SDN and NFV, any OSS system should have real time information held for provisioning and monitoring purpose. OSS and underlying components (be it network, VM, application) should always be in sync.
2. Automated - OSS system should have automated process to make the changes to enviornment also should be smart enogh to identify and record/reconcile changes happened in enviornment
3. Standarisation - Commiunication between OSS and legacy and NFV env. should happen via standard protocol/method such as YANG. Standarisation is key for rolling out new/additional services as well as adopting new/amend vF.
Regards
Lalita
------------------------------
Lalitagauri Dixit
Persistent Systems
------------------------------
Original Message:
Sent: 02-07-2017 16:03
From: Johan Hjalmarsson
Subject: properties of an OSS system
What are the three most important NFV/SDN related features or properties of an OSS system?
------------------------------
Johan Hjalmarsson
Netadmin Systems
------------------------------