zedrouter

type AppCustomBlobsHandler ¶

type AppCustomBlobsHandler struct {
	// contains filtered or unexported fields
}

AppCustomBlobsHandler serves the AppCustom binary blobs

func (hdl AppCustomBlobsHandler) ServeHTTP(w http.ResponseWriter, r *http.Request)

type AppInfoHandler ¶

type AppInfoHandler struct {
	// contains filtered or unexported fields
}

AppInfoHandler provides information about available patches for the application

func (hdl AppInfoHandler) ServeHTTP(w http.ResponseWriter, r *http.Request)

type PatchEnvelopes ¶

type PatchEnvelopes struct {
	sync.RWMutex
	// contains filtered or unexported fields
}

PatchEnvelopes is a structure representing Patch Envelopes exposed to App instances via metadata server for more info check docs/PATCH-ENVELOPES.md Must be created by calling NewPatchEnvelopes()

Internally, PatchEnvelopes structure stores envelopes which come from EdgeDevConfig parsed by zedagent. This envelopes contains both inline binary artifacts which are ready to be downloaded by app instances and volume references, which are handled by volumemgr. So PatchEnvelopes struct has completedVolumes and contentTreeStatus to store information of all volumes and contentTree handled by volumemgr to link them with patch envelope volume references. ContentTreeStatus is used to retrieve SHA of underlying file. App instances are accessing PatchEnvelopes via metadata server handlers, which is calling PatchEnvelopes.Get() method to get list of available PatchEnvelopeInfo to certain App Instance which are stored in currentState. PatchEnvelopes also hasupdateStateNotificationCh channel to receive notification about the need of updating specified PatchEnvelopes. updateStateNotificationCh has length of 1, so update queue will never pile up. When updating state, we iterate through all envelopes, and remove envelopes which are marked in envelopesToDelete boolean map (set). NewPatchEnvelopes() starts goroutine processStateUpdate() which reads from the channel and updates currentState to desired one. In addition, this goroutine publishes status for every PatchEnvelope via pubsub. Note that PatchEnvelopes does not create PubSub, rather used one provided to NewPatchEnvelopes() So it does not have a agentName, but could easily be split into one if needed This way handlers can do work of determining which patch envelopes actually need change (if any) and send back in go routine rest of the update including slow work. Note that this channels are only accessible from the outside by calling a function which returns write-only channel, meaning that updateStateNotificationCh should not be read from anywhere except processStateUpdate() so that there could not be any deadlock.

func NewPatchEnvelopes(log *base.LogObject, ps *pubsub.PubSub) *PatchEnvelopes

func (pes *PatchEnvelopes) EnvelopesInUsage() []string

func (pes *PatchEnvelopes) Get(appUUID string) types.PatchEnvelopeInfoList

func (pes *PatchEnvelopes) UpdateContentTree(ct types.ContentTreeStatus, deleteCt bool)

func (pes *PatchEnvelopes) UpdateEnvelopes(peInfo []types.PatchEnvelopeInfo)

func (pes *PatchEnvelopes) UpdateStateNotificationCh() chan<- struct{}

func (pes *PatchEnvelopes) UpdateVolumeStatus(vs types.VolumeStatus, deleteVolume bool)

type RPCServer ¶

type RPCServer struct {
	// contains filtered or unexported fields
}

RPCServer receives RPC calls from eve-bridge CNI and dispatches them to the main event loop of zedrouter.

func (h *RPCServer) CheckPodConnection(
	args cnirpc.CheckPodConnectionArgs, retval *cnirpc.CheckPodConnectionRetval) error

func (h *RPCServer) ConnectPodAtL2(
	args cnirpc.ConnectPodAtL2Args, retval *cnirpc.ConnectPodAtL2Retval) error

func (h *RPCServer) ConnectPodAtL3(
	args cnirpc.ConnectPodAtL3Args, retval *cnirpc.ConnectPodAtL3Retval) error

func (h *RPCServer) DisconnectPod(
	args cnirpc.DisconnectPodArgs, retval *cnirpc.DisconnectPodRetval) error