Adding a Broadcaster Cluster - Managed

when creating a zen master managed broadcaster cluster, you specify the aws, azure or gcp instance type that will be used for this cluster make sure to select an instance type that supports the type of processing that will be done on this cluster zen master supports both standard cpu instances as well as nvidia gpu instances on aws, azure and gcp (including tesla v100 and t4, which support both hevc decoding and encoding) in addition, zen master supports 5g contribution and distribution using the aws wavelength zone before launching a wavelength zone instance, opt into the wavelength zone service, by enabling the feature via your aws console due to instant type and public ip differences, wavelength zone and non wavelength zone subnets are not interchangeable, and clusters can only choose one for more information, see https //docs aws amazon com/wavelength/latest/developerguide/what is wavelength html https //docs aws amazon com/wavelength/latest/developerguide/what is wavelength html to add a managed broadcaster cluster in the main navigation, click broadcasters click + add the create new broadcaster cluste r screen is displayed in the info section, in the name field, type a logical name for the zixi cluster resource in the tags field, select one or more of the predefined tags from the drop down menu tags are used for access control by selecting a tag you are relating this cluster to an tag tags are associated with certain roles (through the users & roles screen), and roles, in turn, are associated with users and user groups if you would like to create a new tag, see creating a tag docid\ ypm9tw81ap6nq8stkv4rd in the events configuration profile field, select from the dropdown list the profile that you would like to apply to this cluster by default, the defaultprofile is applied events profiles consist of a series of rules that determine precisely how various types of events are logged and what results they trigger in the dns prefix field, enter a unique domain name for sending the streams to/from this cluster select the dtls checkbox if you would like to activate dtls encryption and authentication (this feature is only supported for broadcasters running v12 2+ ) if you selected the dtls checkbox then the ignore dtls certificate when not supported checkbox appears select this checkbox if you would like to enable resources using older versions of zixi software (\<v12 2) that don't support verification of the zen dtls certificate to connect to this cluster select the log scte 35 checkbox if you would like to log scte 35 markers for streams on this cluster to log scte 35 markers, scte 35 needs to be enabled both on the ingest cluster and in the source configuration scte 35 logging is only available for v13 1 40262+ broadcasters select the rtmp server checkbox if you would like to receive rtmp push inputs if you want to configure an alternative path for disaster recovery, in the alternative cluster (disaster recovery) field, select the cluster that will be used as the alternative path for more details, see disaster recovery (alternative path) docid\ poo4zs1 zjra1sndylqe0 in the configuration section, in the management type field, for a managed cluster, select one of the aws , azure or gcp accounts configured in zen master from the list shown under aws, azure or gcp in the drop down menu to create a new cloud service account see linking an aws account docid\ erygxkcufmmz8bakidjz4 , linking an azure account docid\ jsst1kxhrrrfcdyc1lenl or linking a google gcp account docid\ jbuzi2tjvsps3o vzvxxh the configuration fields for the selected type of managed clusters are displayed configuration for managed cluster type fill in your cloud service account details as follows for an aws cluster – in the region field, specify the aws region in the key pair field, select from the drop down list one of the available key pairs to access the cluster if no key pair is displayed, then go to your amazon account to setup your key pair in the vpc field, select from the drop down list one of the available vpc (virtual private cloud) networks to which the cluster will be connected in the subnets field, select from the drop down list one or more of the subnets that are available in this vpc aws wavelength subnets are indicated with "waves bos" for more information about wavelength, see https //docs aws amazon com/wavelength/latest/developerguide/what is wavelength html https //docs aws amazon com/wavelength/latest/developerguide/what is wavelength html in the security groups field, select from the drop down list one or more of the security groups associated with this vpc if no security group is displayed then go to your amazon account to configure your security groups (for guidance in setting up your security groups see amazon security groups https //console aws amazon com/ec2/v2/home?region=us east 1#securitygroups ) in the architecture field, select 64 bit (arm) , or 64 bit (x86) in the instance type field, select from the drop down list one of the available aws instance types that will be used in this cluster in the root device size field, enter the capacity of the hard drive (in gib) for an azure cluster – in the region field, select from the drop down list the location of the account to be used for this cluster in the virtual network field, select from the drop down list a vn in your azure account in the subnet field, select from the drop down list a subnet that is available in the specified vn in the network security group field, select from the drop down list a network security group for this cluster for a gcp account – in the region field, select from the drop down list the region of the gcp account in the zones field, select from the drop down list one or more zones in the specified region in the network field, select from the drop down list one or more of the subnets that are available in the specified region in the machine type field, select from the drop down list the type of machine to be used for the cluster ( note both n1 and n2 machine types are supported ) in the gpu type field, select from the drop down list the type of gpu to be used for the cluster in the root device size field, specify the size of the root device in gib in the activation key field, input the activation key for your zixi broadcaster license in the api user field, enter the username for accessing the zixi broadcaster via api in the api password field, enter the password for accessing the zixi broadcaster via api in the broadcaster version field, select from the drop down list the desired broadcaster version that you would like to run on your cloud service machines the broadcaster versions available for your account can be viewed and modified on the customer portal make sure to select a broadcaster version that supports the type of processing that will be done on this cluster in the authorization mode field, select one of the following options zen master – zen master automatically verifies the authorization for each zen entity (e g sources, channels and targets) that accesses the broadcaster cluster if you would like to allow access to inputs/outputs that are not configured in zen master, then in the allow access… section, select the push inputs and/or pull outputs global password – broadcasters are automatically configured to authorize all connections using a single global password the global password will be used in the source password field when you configure a source in the password field, enter the password or click random to generate a random password free for all – broadcasters will be automatically configured to allow all inputs/outputs to connect select inputs and/or outputs to automatically allow them to connect manual – zen will not authorize connections you will need to authorize each connection independently all authorization modes other than manual will override the authorization configured on your broadcasters therefore, if you have streams on your broadcasters that are not configured on zen master, then any mode other than manual or free for all may interrupt those streams if you would like to adjust the advanced settings, click advanced the advanced settings are displayed advanced settings you can adjust the following settings balance pull targets – select one of the following load balancing methods for pull outputs minimize the number of broadcasters (default)– transfers excess load to other broadcasters only when the allotted capacity on the host broadcaster is filled uniform distribution – distributes the load equally between all available broadcasters under all circumstances http streaming port – you can change the http streaming port from the default ( 7777 ) to a custom port the custom port should match the configuration on the zixi broadcaster elastic ip allocation ids – enter comma separated elastic ip allocation ids elastic ips are a set of fixed ips provided by aws, so that when zen master launches an instance it will assign this instance with one one of these "known" elastic ip addresses this known ip address can be configured in the firewall security solution require elastic ip select this checkbox to prevent zen master from launching an instance if there are no more available elastic ips bandwidth limits – set the bandwidth limits choose one of the two fields input output default hls segment configuration hls/cmaf(dash+fmp4 hls) segment configuration – configure the count and duration parameters for hls and dash segments on this broadcaster cluster the transcode thresholds are used by zen master to determine whether an additional transcoded channel can be added to the broadcaster the following thresholds can be adjusted cpu threshold – percentage of cpu being used memory threshold – percentage of memory being used gpu threshold – percentage of gpu being used adding a broadcaster cluster managed docid 6slx4td zkr2xfho8qz6 gpu memory threshold – percentage of gpu memory being used gpu decoder threshold – percentage of gpu decoder pipeline being used gpu encoder threshold – percentage of gpu encoder pipeline being used enable real time broadcaster process priority this setting is deselected by default you can increase the broadcaster's process priority by selecting it this may be beneficial for sending streams to highly sensitive irds however, this should not be done without consulting with your customer success agent zen master will expect a response form the external server, consisting of a json object the following details need to be configured server endpoint an external authorization url for the server endpoint optional authorization header schema and credentials to access the service external authorization zen master can, in addition to its standard internal authorization process, redirect the authorization of connections to an external service for example, an external pay per view application, which confirms that a requesting end device belongs to an account that has paid for a live event server endpoint an external authorization url for the server endpoint optional authorization header schema and credentials if you would like to track usage for this broadcaster, enter your billing code details, see billing codes docid\ lalxj n928tegcpdpbirj (supported for broadcasters v14 8+) if you would like to install agentz automatically, select the install agentz automatically checkbox agent z is a sidecar tool that sits on a zixi broadcaster, it acquires the system health data and other statistics locally and pushes it to zen master by enabling this option, zen master will automatically install agentz on any existing and future broadcasters connected to the cluster the feature is off by default due to agentz installation requiring a restart, zen master will not auto install agentz on a broadcaster that already contains any inputs to avoid disturbing active streams click save the new broadcaster cluster is created in the system and added to the list of broadcaster clusters the status should change from pending to ok after a few minutes notes the gpu thresholds are only relevant for transcoding workflows using intel quick sync or nvidia gpus