Age | Commit message (Collapse) | Author | Files | Lines |
|
This patch enhances the status query API.
- The ResourceBundleState CRD is modified to just use the
k8s Pod structure instead of a customized struct.
- Status queries can either present results showing
the rsync status of the composite app and resources
or from information received from the cluster via
the ResourceBundleState CR
- Query parameters are provided to the API call to
customize the query and response
- Support for querying status of cluster network
intents is added
Issue-ID: MULTICLOUD-1042
Signed-off-by: Eric Multanen <eric.w.multanen@intel.com>
Change-Id: Icca4cdd901e2f2b446414fade256fc24d87594cd
|
|
Changes made to remove dependency of rsyn
registraion from orchestrator need to be added
to ncm as well.
Issue-ID: MULTICLOUD-1196
Signed-off-by: Eric Multanen <eric.w.multanen@intel.com>
Change-Id: Ie572a127fd87cf50a1bb03163d98d3ebe901437e
|
|
Add support in the AppContext for managing an AppContext
(composite app level) status value.
Also adds support for tracking rsync status at the resource
level.
A mechanism for tracking history at the controlling resource
level (i.e. DeploymentGroupIntnt or Cluster) is added, in part,
so that all AppContexts associated can be deleted when
the resource is eventually deleted.
Issue-ID: MULTICLOUD-1042
Change-Id: I3d0a9a97ea45ca11f9f873104476e4b67521e56a
Signed-off-by: Eric Multanen <eric.w.multanen@intel.com>
|
|
Add a StateInfo structure to the Cluster and
Deployment-Intent-Group resources to keep track of
the lifecycle state of these resources. Moved the
appcontext id that was being kept into this structure
as well. Enabled the approve state (and API) for
the deployment intent group.
Issue-ID: MULTICLOUD-1042
Signed-off-by: Eric Multanen <eric.w.multanen@intel.com>
Change-Id: I36602d8a0658d9d6d37b8799f9a372a7d1042496
|
|
Complete the basic terminate support for the
orchestrator and ncm services.
1. When terminate REST API is invoked on a deployment
intent group, call the uninstall grpc api to rsync
and then remove the app context.
2. When terminate REST API is invoked on a cluster,
add the uninstall grpc api call to rsync to remove
the network resources from the clusters.
Issue-ID: MULTICLOUD-1040
Signed-off-by: Eric Multanen <eric.w.multanen@intel.com>
Change-Id: I181e891a8c7c973970af061f9ff07d80c3bb64f9
|
|
Split out the cluster provider and cluster APIs
and packages into a separate microservice to align
with the architecture.
Issue-ID: MULTICLOUD-1029
Signed-off-by: Eric Multanen <eric.w.multanen@intel.com>
Change-Id: I08f357b5a488004a2389b72a178ae33e101d1540
|
|
Reorginize the ncm packges to delineate
- cluster provider and cluster management
- virtual and provider netowrk intent management
- intent scheduler
- internal ovn4k8s network controller
Overall, no code changes, just moving things around.
Issue-ID: MULTICLOUD-1029
Signed-off-by: Eric Multanen <eric.w.multanen@intel.com>
Change-Id: I3d43c7e4eb6f285b51c0385ba18626d3511a14f5
|
|
Split out part of ncm microservice to act as the
Onv4k8s network action controller for the orchestrator.
No code changes really - just moving around to fit the
architectural plan.
Issue-ID: MULTICLOUD-1029
Signed-off-by: Eric Multanen <eric.w.multanen@intel.com>
Change-Id: I17292ac72d041050269f05fc4a0c2a6ca741aeb5
|
|
Correct yaml format of Network and ProviderNetwork
CRs produced by ncm so that they can be deployed in
a cluster.
Issue-ID: MULTICLOUD-1072
Signed-off-by: Eric Multanen <eric.w.multanen@intel.com>
Change-Id: I27e55c0c7428ccee6ddb720445e104054eefcee3
|
|
Create AppContext instruction records at the
app and resource levels when handling the apply
api for network and providernetwork intents.
Issue-ID: MULTICLOUD-1029
Signed-off-by: Eric Multanen <eric.w.multanen@intel.com>
Change-Id: I3c82087273278b2503959664f0a8ee4e34eb0cd2
|
|
Adds a grpc client to resource synchronizer to ncm
to handle network and providernetwork.
Issue-ID: MULTICLOUD-1029
Signed-off-by: Eric Multanen <eric.w.multanen@intel.com>
Change-Id: I45646d66ab1ec79818d0942694f8238718c407b3
|
|
Issue-ID: MULTICLOUD-1064
Signed-off-by: Rajamohan Raj <rajamohan.raj@intel.com>
Change-Id: Ie4a914adbb20f6227dcba9c380a9d416f5274ad3
|
|
Add a contextupdate grpc server to the ncm service.
Issue-ID: MULTICLOUD-1029
Signed-off-by: Eric Multanen <eric.w.multanen@intel.com>
Change-Id: I38caa625c028baac06a6202f03b86d0f2bf38126
|
|
|
|
The signature of two functions of upstream code
in orchestration is to be changed.
The new function signature for changes in appcontext.go:
AddResource(handle interface{}, resname string, value []byte)
UpdateResourceValue(handle interface{}, value []byte)
The above code shall be pushed in the next patch for
orchestration
Issue-ID: MULTICLOUD-1064
Signed-off-by: Rajamohan Raj <rajamohan.raj@intel.com>
Change-Id: I58db28e2e0ea27fba9b88839156a43517cdad1c9
|
|
Adds API for managing Network Chain intents for
composite applications.
Issue-ID: MULTICLOUD-1029
Signed-off-by: Eric Multanen <eric.w.multanen@intel.com>
Change-Id: Ie3d4e8f1e3179397d86829d951e2bb877597b38d
|
|
Apply workload network intents to indicated
resources in the AppContext.
This will add/update network annotations for
pods or resources that have pod templates.
Issue-ID: MULTICLOUD-1029
Signed-off-by: Eric Multanen <eric.w.multanen@intel.com>
Change-Id: I9ae4387a8c28a95510406da361cfef3f8257bc80
|
|
|
|
NCM shall be like a library which orchestrator shall
call as and when required. NCM will assume that whenever
orchestrator calls it all the validation of orchestrator components
is done, so NCM shall not validate orchestrator components.
Otherwise, if NCM calls the orchestration, this will result
in cyclic import issue.
Issue-ID: MULTICLOUD-1041
Signed-off-by: Rajamohan Raj <rajamohan.raj@intel.com>
Change-Id: Ie352c730ffd39863d6de23d6a9a9a934f460392b
|
|
Support POST API to 'apply' and 'terminate' network and
providernetwork intents for a given cluster.
Issue-ID: MULTICLOUD-1029
Signed-off-by: Eric Multanen <eric.w.multanen@intel.com>
Change-Id: I8c9bae9e93aeeb68654eaab1f15de9883c22215c
|
|
Includes network controller intent and underlying
network workload intent and workload interface
intent APIs.
Issue-ID: MULTICLOUD-1029
Signed-off-by: Eric Multanen <eric.w.multanen@intel.com>
Change-Id: I9bb34e42785b16f39af81335b1f94dd5bb15d931
|
|
Add Query endpoint and implements returning list
of clusters with label.
Issue-ID: MULTICLOUD-922
Signed-off-by: Ritu Sood <ritu.sood@intel.com>
Signed-off-by: Eric Multanen <eric.w.multanen@intel.com>
Change-Id: I879b5e9002a0cbc9191abb99f1e164ee2b1c6581
|
|
Add API for CRUD operations to manage network
and provider-network intent resources.
Issue-ID: MULTICLOUD-1029
Signed-off-by: Eric Multanen <eric.w.multanen@intel.com>
Change-Id: If3c71691b3825db50eacdb0ea87b0d5c436ad80f
|
|
Creates a new network customization and configuration
service. Seed it by moving the cluster-provider and
cluster API from the orchestrator service to this new
service. More APIs to follow.
Just put a Dockerfile in the ncm/scripts directory for now.
See: https://wiki.onap.org/pages/viewpage.action?pageId=79201398
Issue-ID: MULTICLOUD-1029
Signed-off-by: Eric Multanen <eric.w.multanen@intel.com>
Change-Id: Iea1b1151e5f87fecaca9cfe8c9746a59eb447a7a
|