E2E Networks Documentation E2E Networks documentation Skip to content E2E Cloud Docs E2E Networks TIR Toggle navigation menu Login Sign Up E2E Networks documentation K Docs E2E Networks TIR Myaccount Getting Started with Myaccount SignUp Process for Indian Customers Customer validation Process for Indian Customers SignUp Process for International Customers Customer Validation Process for International Process Customer Validation Process for Contact Persons Domestic Customer Validation Process FAQs International Customer Validation Process FAQs Sign In Process Release Notes Compute Nodes Virtual Compute Nodes Monitoring 1Click Deployment Active Directory GPU GPU Cloud EQS Introduction Appliance Load Balancer Appliance Auto Scaling Introduction Concepts Define Scale Groups FaaS Function as a Service FaaS Network CDN VPC How to reserve an IP address Reserve IP Pool DNS Custom Reverse DNS Firewall Security Group Tag Security Firewall Bitninja Best Practices SSH Key Management Audit Logs Password Policy 2Factor Authentication Others License Management User Management Purchase SSL CertbotPlugin Apply or Redeem Coupon Code Account Statement Cloud Platform Support Introduction Platform Support Policy FAQ E2Es MyAccount FAQs Code of Conduct of Directors and Senior Management CSR Policy Whistle blower policy Jitsi Meet Mod Evasive Multisite using cPanel Softaculous Copying data from Linux to Windows using WinSCP Migrate MySQL Database Between DBaaS Manage MySQL Abuse Abuse Logs Abuse Attacks Spam Mails Phishing Complaint Copyright Complaint Billing Payment Payment Method EMandate Redeem Coupon Customer Details Updation Setup AutoDebit feature TDS Deduction process Declaration us 206AB Minimum Billing Provisioning and Deprovisioning Process View Invoice and Payment Prepaid Billing Set up Infra Credits Balance Alert Whatsapp notification for Payment reminder Restore Service on a Suspended Account for NonPayment Database Database Database PostgreSQL Parameter Group MongoDB mariaDB Storage Storage Block Storage Object Storage CDP Backup Scalable File System Kubernetes Kubernetes Service Kubernetes Kubernetes Marketplace Monitoring Stack Cert Manager Nginx Ingress Controller Troubleshooting Argo CD Declarative GitOps CD for Kubernetes Deploy to Kubernetes using Argo CD and GitOps Jenkins CI Tool Setup Jenkins On Kubernetes Cluster Ansible CD Tool Istio Service Connecting to Dbaas FAQS Container Registery Container Registery API Developers Guide API SDK E2E CLI Tool Introduction Terraform Terraform Getting Started e2enode Resource Node Plans e2eimage Resource AIML TIR AI Release Notes TIR AI Platform Introduction Getting Started Howto Guides Projects Notebooks Committed Notebook GPU H100 Plans Datasets Model Repository Model Endpoints Pipeline Run Scheduled Run Fine Tuning Models Model Playground Samples and Tutorials API Tokens SSH Key Container Team Features Settings Analytics Billing AIML Tutorials Finetune LLMA with Multiple GPUs Deploy Inference for LLMA 2 Deploy Inference for Codellama Deploy Inference for Stable Diffusion v21 Finetune Stable Diffusion model on TIR Deploy Inference for MPT7BCHAT Custom Containers in TIR Fine Tuning Bloom Natural Language Queries to SQL wth Code Llama E2E Networks Documentation Welcome to E2E Networks platform documentation E2E Networks Limited is Indias leading NSElisted AIfirst hyperscale cloud provider Here users will find detailed guides tutorials and troubleshooting tips covering a wide range of topics from CPU and GPU compute usage to TIR AI Platform Kubernetes services Terraform our ecosystem of cloud technologies our APIs and SDK storage solutions and about our DBaaS platform You will also find help on our Billing and Payment system security and our processes for handling abuse You will also find tutorials that help you get started with building applications in the AIML domain Finally you can also check out our release notes for latest features fixes and updates released on Myaccount Getting Started To get started head to Myaccount and follow the sign up process explained here Note that the process is slightly different for Indian individiuals Indian organizations and International organizations Click here to get started Our AIFirst Infrastructure E2E Networks advanced cloud GPUs offer developers unprecedented access to highperformance computing resources essential for tackling intensive tasks like machine learning deep learning and complex data analytics Our GPUs ranging from HGX 8xH100 A100 clusters L4OS T4 and others are integrated into E2Es cloud infrastructure and provide a highend platform to developers for AI inference and development Get started with our GPU nodes here TIR AI Platform TIR is a modern AI Development Platform designed to tackle the friction of training and serving large AI models TIR uses highly optimised GPU containers NGC preconfigured environments pytorch tensorflow triton automated API generation for model serving shared notebook storage and much more Learn more about TIR here On this page Getting Started Our AIFirst Infrastructure TIR AI Platform Products TIR AI Platform GPU Dedicated Compute CPU Intensive Cloud High Memory Cloud Linux Smart Dedicated cPanel Linux Cloud Windows Cloud Windows SQL Cloud Plesk Windows Cloud GPU Smart Dedicated Load Balancer Company About Us Meet the Team Become a Partner E2E in Media Testimonials Investors Careers Contact Us Contact Sales Escalation Matrix Service Level Agreement Terms of Service Privacy Policy Refund Policy Policy FAQ Resources Blog Events Service Health Status Help White Papers Ecosystem Enablers Customers Certifications Countries Served FAQs E2E Networks Limited E2E Networks Limited is a NSE Listed AIFirst Hyperscale Cloud Computing Platform CIN Number L72900DL2009PLC341980 Copyright 2023 E2E Networks Limited


Introduction E2E Networks documentation Skip to content E2E Cloud Docs E2E Networks TIR Toggle navigation menu Login Sign Up E2E Networks documentation K Docs E2E Networks TIR Myaccount Getting Started with Myaccount SignUp Process for Indian Customers Customer validation Process for Indian Customers SignUp Process for International Customers Customer Validation Process for International Process Customer Validation Process for Contact Persons Domestic Customer Validation Process FAQs International Customer Validation Process FAQs Sign In Process Release Notes Compute Nodes Virtual Compute Nodes Monitoring 1Click Deployment Active Directory GPU GPU Cloud EQS Introduction How to Create EQS Actions Add Queue under tab Actions for queue service Using SDK Appliance Load Balancer Appliance Auto Scaling Introduction Concepts Define Scale Groups FaaS Function as a Service FaaS How to Create Functions Functions Information Network CDN VPC How to reserve an IP address Reserve IP Pool DNS Custom Reverse DNS Firewall Security Group Tag Security Firewall Bitninja Best Practices SSH Key Management Audit Logs Password Policy 2Factor Authentication Others License Management User Management Purchase SSL CertbotPlugin Apply or Redeem Coupon Code Account Statement Cloud Platform Support Introduction Platform Support Policy FAQ E2Es MyAccount FAQs Code of Conduct of Directors and Senior Management CSR Policy Whistle blower policy Jitsi Meet Mod Evasive Multisite using cPanel Softaculous Copying data from Linux to Windows using WinSCP Migrate MySQL Database Between DBaaS Manage MySQL Abuse Abuse Logs Abuse Attacks Spam Mails Phishing Complaint Copyright Complaint Billing Payment Payment Method EMandate Redeem Coupon Customer Details Updation Setup AutoDebit feature TDS Deduction process Declaration us 206AB Minimum Billing Provisioning and Deprovisioning Process View Invoice and Payment Prepaid Billing Set up Infra Credits Balance Alert Whatsapp notification for Payment reminder Restore Service on a Suspended Account for NonPayment Database Database Database PostgreSQL Parameter Group How to create Parameter Group MongoDB mariaDB Storage Storage Block Storage Object Storage CDP Backup Scalable File System Kubernetes Kubernetes Service Kubernetes Kubernetes Marketplace Monitoring Stack Cert Manager Nginx Ingress Controller Troubleshooting Argo CD Declarative GitOps CD for Kubernetes Deploy to Kubernetes using Argo CD and GitOps Jenkins CI Tool Setup Jenkins On Kubernetes Cluster Ansible CD Tool Istio Service Connecting to Dbaas FAQS Container Registery Container Registry Simplifying Pull Operations with UserFriendly Interface API Developers Guide API SDK E2E CLI Tool Introduction Terraform Terraform Getting Started e2enode Resource Node Plans e2eimage Resource AIML TIR AI Release Notes TIR AI Platform Introduction Getting Started Howto Guides Projects Notebooks Committed Notebook GPU H100 Plans Datasets Model Repository Model Endpoints Pipeline Run Scheduled Run Fine Tuning Models Model Playground Samples and Tutorials API Tokens SSH Key Container Team Features Settings Analytics Billing AIML Tutorials Finetune LLMA with Multiple GPUs Deploy Inference for LLMA 2 Deploy Inference for Codellama Deploy Inference for Stable Diffusion v21 Finetune Stable Diffusion model on TIR Deploy Inference for MPT7BCHAT Custom Containers in TIR Fine Tuning Bloom Natural Language Queries to SQL wth Code Llama E2E Networks documentation Application Scaling on E2E Cloud Introduction Introduction E2E Auto scaling enables you to dynamically scale compute nodes based on varying workloads and a defined policy Using this feature you can meet the seasonal or varying demands of infrastructure while optimizing the cost The core unit of EAS is a scale group The following list covers the features and capabilities of scale groups Rule based Policy setup for adding nodes based on workload Integration with Load Balancer to automatically list or delist backend servers Automatic removal of nodes when utilization falls below a set threshold SSH access to each node enables activities like log viewing debugging etc Before you define your first scale group we recommend familiarizing yourself with concepts and terminologies Concepts Application Scaling helps you offer consistent performance for your endusers during high demand and also reduce your spend during periods of low demand The following section covers the key terminologies used through this document Scaler Scaler is E2E service that manages Application Scaling functionality Scale Group Scale Groups represent the nodes launched by Scaler Each group is destined to adhere to a scaling policy eg Add a compute node when CPU utilization on an existing node hovers at 70 for 20 seconds Group nodes The nodes in a scale group are dynamically added or removed These nodes will be referred to as Group nodes or just nodes in the rest of the document The lifecycle of group nodes starts with the creation of scale groups and ends with the termination of the group You will be charged for the time between start action of a node and the time of termination Saved Image Due to the dynamic nature of nodes you would want to automate the launch sequence of the application too This is where the saved image comes into play A saved image is nothing but a compute node that you had saved and has the capability to launch your application at the startup Compute Plan The compute plan or plan is where you select infrastructure or hardware requirements for your group nodes It need not be same as the plan you had used to create your saved image This is a plan sequence you are most likely to follow when defining application scaling Create a node with a conservative plan for application eg C Series 1 CPU 1GB Add launch sequence to autoinstall and start your application during startup Create a scale group with an actual plan you need for your production servers eg C series 16 CPU 64 GB Scaling Policy A scaling policy determines the lifecycle of group nodes It consists of an expression that contains the following factors Min nodes Max nodes Desired nodes or Cardinality Watch Period and Period Duration Cooldown A scaling policy determines how you want to add a node to the group A negative policy is automatically created by Scaler to handle termination of nodes For example When a user sets an expression of CPU 80 for upscaling the scaler will automatically create a downscaling policy of CPU 80 The downscaling policies will be internally managed by the scaler Min and Max nodes Min and Max nodes determine the maximum or minimum guarantees from your scale group Cardinality or Desired Nodes Though the actual number of group nodes is decided by scaler through policy configuration you have an option to influence this setting on certain occasions One of such occasions is when you perform code or image updates You could launch extra nodes that will absorb the changes and then manually delete the existing nodes that have an older version of your code Keep it simple Start with 2 nodes and let the scale group take over Performance or Target Metric At this time a scaling policy only supports CPU Utilization Watch Periods It is normal to see CPU spikes on the servers but what you want is a consistent spike that lasts for a period of time to make a scaling decision A watch period has two parts Periods and Period Duration A duration determines how long a period lasts and the number of periods determines how long the watch lasts Lets go through an example to understand this better Note Consider this scaling policy Expression CPU 75 Watch Period 2 Period Duration 10 seconds The scaler will watch out for 2 consecutive periods of 10 seconds each when the CPU Utilization stays at above 75 And when such condition occurs the scaling operation will be initiated Cooldown A cooldown is a full period when all scaling operations are blocked It typically starts right after a scaling operation The idea of cooldown is to wait and watch for impact of a scale operation before taking further actions The default is 150 secs Load Balancer Load balancers form the entry doors when your scaling applications While the actual group nodes and their IP may keep on changing the load balancer will enable consistent access for the external world Tip Always bundle your scale groups with a load balancer Define Scale Groups Application scaling helps you optimize your infrastructure by automatically adjusting the number of compute nodes based on a predefined policy You can define a scale group a pool of compute nodes for any web frontend or backend application and provide consistent performance to your endusers Before you Begin To save an image of a Virtual Node it must be powered down For this click on the Power Off under the Actions section After powering off Node now again click on Action button and then click on Save Image button Steps to Define Scale Groups Go to My Account Go to Compute Auto Scaling Click on Create a new Group Select a Saved Image that can launch your application at startup To create a new group click on Create a new Group button Select the image you want to use to create a new group After selecting the image select the plan according to your requirement Elastic Policy Elastic policies are designed to ensure that the infrastructure scales up or down automatically based on predefined conditions or metrics These conditions or metrics can include CPU utilization network traffic request latency or any other relevant performance indicators After selecting the plan give the name of your scale group select the parameters and select policy The Elastic Policy allows you to choose between two scaling policies Default or Custom If you choose Default the scaling will be based on CPU or Memory utilization If you choose Custom you can specify a custom attribute that will be used to determine the scaling Here is a more detailed explanation of the two policies you have two types of policy parameters DEFAULT and CUSTOM Default In Default you can select policy parameter type CPU or MEMORY CPU This policy scales the number of resources based on the CPU utilization When the CPU utilization reaches a certain threshold the number of resources will be increased according to the policy which you have set When the CPU utilization decreases the number of resources will be decreased Memory This policy scales the number of resources based on the Memory utilization When the Memory utilization reaches a certain threshold the number of resources will be increased according to the policy which you have set When the Memory utilization decreases the number of resources will be decreased Custom In a Custom policy you have two methods to specify a custom attribute 1 This policy allows you to specify a custom attribute that will be used to determine the scaling For example you could specify the memory utilization or the number of requests When the value of the custom attribute reaches a certain threshold the number of resources will be increased When the value of the custom attribute decreases the number of resources will be decreased Note policy parameter name field is mendatory 2 Once an autoscaling configuration is created with custom parameters youll receive a CURL command for updating the custom parameter value This command can be used within scripts hooks cron jobs and similar actions When the value of this custom parameter reaches a specific threshold the number of resources will increase Conversely when the value decreases the number of resources will decrease Note Please note that the default value of the custom parameter is set to 0 The choice of which policy to use depends on your specific needs If you want the scaling to be based on CPU utilization then the CPU policy is a good choice If you want the scaling to be based on a custom attribute then the Custom policy is a good choice Custom Policy If you select the custom policy then specify any custom attribute such as memorydiskiops or any other custom policy name After selecting the options click on Create Scale button Manage Custom policy The custom policy feature in auto scaling enables you to define your own custom attribute The auto scaling service utilizes this attribute to make scaling decisions The customer is responsible for setting this value on the service VM To configure the custom attribute on the VM the customer should first set up the attribute on an existing VM Afterward they need to create a saved image from that VM and use it to create the scaler service Note The custom policy attribute must be configured on the image used to create the Scaler service Custom Policy Name The Custom Policy Name field is where you enter the name of the custom attribute that you want to use to monitor your service This attribute can be any name that you choose but it is helpful to use names that are descriptive of the aspect of your service that you are monitoring For example you could use the names MEMORY for memory usage NETTX for Network traffic DISKWRIOPS for disk write operations etc Node utilization section Specify the values that will trigger a scaleup increase in cardinality or scaledown decrease in cardinality operation based on your preferences Scaling Period Policy You need to define the watch period duration of each period and cooldown period Note If your custom policy names are MEMORY NETTX NETRX DISKWRIOPS DISKRDIOPS DISKWRBYTES or DISKWRIOPS you do not need to worry about anything else However if you wish to adjust the cardinality of your autoscaling service based on different attributes you must configure them through your node Scaling incrementing and decrementing occurs based on the average value of the custom policy attribute To set custom attributes on service nodes follow these steps Create a new node Establish an SSH connection to that node Add the script provided below to your node and may set up a cron job for it Let us assume that you have set Custom policy name as CUSTOMATT and max utilization is set at 60 units and minimum utilization is set at 30 units then the cardinality will get increase when the value of the CUSTOMATT goes more than 60 units and the cardinality will get decrease if the value of the CUSTOMATT falls below 30 units If your goal is to adjust the cardinality based on the percentage of memory utilization you need to assign the CUSTOMATT attribute to the node This attribute will monitor memory utilization through the script To achieve this create a cron job that monitors memory utilization and updates the attribute periodically When writing the script youll need to obtain the following information ONEGATEENDPOINT TOKENTXT and VMID You can find these details at the following location varrunonecontextoneenv To create the script in a sh file follow these steps Create or update the file with the desired file name like filenamesh Inside the script file filenamesh you can begin writing your script Now you have two options to write a script inside the file filenamesh either use the option1 or option 2 to write a script Option1 TMPDIRmktemp d echo TMPDIRmetrics MEMTOTALgrep MemTotal procmeminfo awk print 2 MEMFREEgrep MemFree procmeminfo awk print 2 MEMUSEDMEMTOTALMEMFREE MEMUSEDPERC0 if z MEMTOTAL MEMTOTAL gt 0 then MEMUSEDPERCecho MEMUSED MEMTOTAL awk printf 2f 100 1 2 fi CUSTOMATTRMEMUSEDPERC echo CUSTOMATTR CUSTOMATTR TMPDIRmetrics VMIDsource varrunonecontextoneenv echo VMID ONEGATEENDPOINTsource varrunonecontextoneenv echo ONEGATEENDPOINT ONEGATETOKENsource varrunonecontextoneenv echo TOKENTXT curl X PUT ONEGATEENDPOINTvm header XONEGATETOKEN ONEGATETOKEN header XONEGATEVMID VMID databinary TMPDIRmetrics Option2 MEMTOTALgrep MemTotal procmeminfo awk print 2 MEMFREEgrep MemFree procmeminfo awk print 2 MEMUSEDMEMTOTALMEMFREE MEMUSEDPERC0 if z MEMTOTAL MEMTOTAL gt 0 then MEMUSEDPERCecho MEMUSED MEMTOTAL awk printf 2f 100 1 2 fi VMIDsource varrunonecontextoneenv echo VMID onegate vm update VMID data CUSTOMATTRMEMUSEDPERC Now To make the filenamesh file executable execute the following command chmod x filenamesh To run the filenamesh script use the following command filenamesh This will execute the script and perform its intended actions But for continuous monitoring of your attribute there is a need to make a cron of your script So for this in the terminal execute crontab e You will be prompted to specify a file where you need to provide the scheduled time for the cron job and the location of the script Example pathtoyourfilenamesh rootfilenamesh Afterward create an image of that node Launch your auto scale group using a custom policy name make sure to use the same name during configuration This setup will monitor the percentage of memory utilization and store it in the specified custom attribute CUSTOMATTR Based on the values which you have provided for cardinality increment and decrement your scheduled actions will be performed Note Upscaling and downscaling will be determined based on the average attribute value across all launched nodes To see the set attributes you can use given blow command onegate vm show VMID json After run above command the detail will be shown like this VM NAME machinename ID machineid STATE machinestate LCMSTATE machinelcmstate USERTEMPLATE CUSTOMATTR setattribute DISTRO distro HOTRESIZE CPUHOTADDENABLED NO MEMORYHOTADDENABLED NO HYPERVISOR kvm INPUTSORDER LOGO imageslogoscentospng LXDSECURITYPRIVILEGED true MEMORYUNITCOST MB MYACCOUNTDISPLAYCATEGORY Linux Virtual Node OSTYPE CentOS75 SAVEDTEMPLATEID 0 SCHEDDSREQUIREMENTS ID0 SCHEDREQUIREMENTS ID10 ID11 SKUTYPE skutype TYPE Distro TEMPLATE NIC IP ipadd MAC macadd NAME nicname NETWORK yournetwork NICALIAS To see the VMID you can use given blow command onegate vm show Output will be like this VM 8 NAME web0service1 STATE RUNNING IP 19216812223 Schedule Policy Schedule Policy Autoscaling schedule policy is a feature that allows you to define a predetermined schedule for automatically adjusting the capacity of your resources A scheduled autoscaling policy is a type of scaling policy that allows you to scale your resources based on a defined schedule For example you may use a scheduled autoscaling policy to increase the number of instances in your service during peak traffic hours and then decrease the number of instances during offpeak hours Recurrence In auto scaling recurrence refers to the ability to schedule scaling actions to occur on a recurring basis This can be useful for applications that experience predictable traffic patterns such as a website that receives more traffic on weekends or a web application that receives more traffic during peak business hours Upscale and downscale recurrence in auto scaling refers to the process of increasing and decreasing the number of resources in an Auto Scaling group respectively This can be done on a recurring basis such as every day week or month Cron To configure recurrence in auto scaling you need to specify a cron expression A cron expression is a string that specifies the time and frequency of the scaling action For example the cron expression 0 0 specifies that the scaling action should be run at 0000 midnight every day Upscale recurrence You can specify the cardinality of nodes at a specific time by adjusting the field in the cron settings Ensure that the value is lower than the maximum number of nodes you had previously set Downscale recurrence You can specify the cardinality of nodes at a specific time by adjusting the field in the cron settings Ensure that the value is greater than the maximum number of nodes you had previously set Now if you want to choose scheduled policy as your choice of option then select Schedule Policy in place of Elastic Policy and then set the upscale and downscale recurrence and click on Create Scale button Elastic and Scheduled Policy If the user desires to create a scaler service using both options they can choose the Both policy option configure the parameters and proceed with creating the scalar service To see the details of the scale group click on Scale Group Details To view the details of the active nodes click on Active Node Details tab To View the details of the Terminated Node click on Terminated Node Details tab To View the details of the associated networks click on the Network tab To View the details of the Attached LB click on Attached LB tab To View the details of the Monitoring click on Monitoring tab To View the details of the Security Group click on Security group tab To View the details of the Logs click on Logs tab Actions Resize Service To resize the services click on 3 dots and click on resize services option StartStop Action Introduction The startstop actions in the autoscaling service are designed to manage the state of the service allowing users to start or stop their instances as needed This documentation provides a detailed guide on how to utilize these actions effectively Stop Action The stop action is used to halt the service within the autoscaling infrastructure Process When initiating a stop action the service will transition to a stopped state after a brief period State The service will be marked as stopped and the desired nodes will be set to zero Billing During the stopped state billing for the service will be paused ensuring cost savings for the user Start Action The start action is employed to commence the service within the autoscaling environment Process Upon executing a start action the service will transition to a running state after a short duration State The service will be in a running state maintaining the same configuration as before with desired nodes set to the minimum node count specified Billing Billing for the service resumes immediately upon starting allowing for seamless operation with updated configurations Conclusion Utilizing the start and stop actions provides users with the ability to efficiently manage their autoscaling service controlling costs and resources effectively For further assistance or inquiries please reach out to our support team Delete To delete the service click on Delete button To edit the Scale groups details like parameters policies then click on edit icon To edit the Scale group prarameters click on edit icon After doing changes click on right icon to update the scale group parameter To edit the Scale group policy click on edit icon To select Elastic policy click on edit icon and select from dropdown After selcting Elastic policy then want to change in CPU utilisation watch period duration cooldown After doing changes click on update button To select Scheduled policy click on edit icon and select from dropdown After selecting Scheduled policy then want to change in Upscale Recurrence Upscale Desired Nodes etc After doing changes click on update button To select both policy ie Elastic Scheduled policy click on edit icon and select from dropdown After doing changes in the form click on update button Note Deleting the saved image is not allowed when it is associated with a Scale group You need to first terminate the associated scale group to delete this saved image On this page Concepts Scaler Scale Group Group nodes Saved Image Compute Plan Scaling Policy Min and Max nodes Cardinality or Desired Nodes Performance or Target Metric Watch Periods Cooldown Load Balancer Define Scale Groups Elastic Policy Custom Policy Manage Custom policy Schedule Policy Elastic and Scheduled Policy Actions Introduction Products TIR AI Platform GPU Dedicated Compute CPU Intensive Cloud High Memory Cloud Linux Smart Dedicated cPanel Linux Cloud Windows Cloud Windows SQL Cloud Plesk Windows Cloud GPU Smart Dedicated Load Balancer Company About Us Meet the Team Become a Partner E2E in Media Testimonials Investors Careers Contact Us Contact Sales Escalation Matrix Service Level Agreement Terms of Service Privacy Policy Refund Policy Policy FAQ Resources Blog Events Service Health Status Help White Papers Ecosystem Enablers Customers Certifications Countries Served FAQs E2E Networks Limited E2E Networks Limited is a NSE Listed AIFirst Hyperscale Cloud Computing Platform CIN Number L72900DL2009PLC341980 Copyright 2023 E2E Networks Limited


License Management E2E Networks documentation Skip to content E2E Cloud Docs E2E Networks TIR Toggle navigation menu Login Sign Up E2E Networks documentation K Docs E2E Networks TIR Myaccount Getting Started with Myaccount SignUp Process for Indian Customers Customer validation Process for Indian Customers SignUp Process for International Customers Customer Validation Process for International Process Customer Validation Process for Contact Persons Domestic Customer Validation Process FAQs International Customer Validation Process FAQs Sign In Process Release Notes Compute Nodes Virtual Compute Nodes Monitoring 1Click Deployment Active Directory GPU GPU Cloud EQS Introduction How to Create EQS Actions Add Queue under tab Actions for queue service Using SDK Appliance Load Balancer Appliance Auto Scaling Introduction Concepts Define Scale Groups FaaS Function as a Service FaaS How to Create Functions Functions Information Network CDN VPC How to reserve an IP address Reserve IP Pool DNS Custom Reverse DNS Firewall Security Group Tag Security Firewall Bitninja Best Practices SSH Key Management Audit Logs Password Policy 2Factor Authentication Others License Management User Management Purchase SSL CertbotPlugin Apply or Redeem Coupon Code Account Statement Cloud Platform Support Introduction Platform Support Policy FAQ E2Es MyAccount FAQs Code of Conduct of Directors and Senior Management CSR Policy Whistle blower policy Jitsi Meet Mod Evasive Multisite using cPanel Softaculous Copying data from Linux to Windows using WinSCP Migrate MySQL Database Between DBaaS Manage MySQL Abuse Abuse Logs Abuse Attacks Spam Mails Phishing Complaint Copyright Complaint Billing Payment Payment Method EMandate Redeem Coupon Customer Details Updation Setup AutoDebit feature TDS Deduction process Declaration us 206AB Minimum Billing Provisioning and Deprovisioning Process View Invoice and Payment Prepaid Billing Set up Infra Credits Balance Alert Whatsapp notification for Payment reminder Restore Service on a Suspended Account for NonPayment Database Database Database PostgreSQL Parameter Group How to create Parameter Group MongoDB mariaDB Storage Storage Block Storage Object Storage CDP Backup Scalable File System Kubernetes Kubernetes Service Kubernetes Kubernetes Marketplace Monitoring Stack Cert Manager Nginx Ingress Controller Troubleshooting Argo CD Declarative GitOps CD for Kubernetes Deploy to Kubernetes using Argo CD and GitOps Jenkins CI Tool Setup Jenkins On Kubernetes Cluster Ansible CD Tool Istio Service Connecting to Dbaas FAQS Container Registery Container Registry Simplifying Pull Operations with UserFriendly Interface API Developers Guide API SDK E2E CLI Tool Introduction Terraform Terraform Getting Started e2enode Resource Node Plans e2eimage Resource AIML TIR AI Release Notes TIR AI Platform Introduction Getting Started Howto Guides Projects Notebooks Committed Notebook GPU H100 Plans Datasets Model Repository Model Endpoints Pipeline Run Scheduled Run Fine Tuning Models Model Playground Samples and Tutorials API Tokens SSH Key Container Team Features Settings Analytics Billing AIML Tutorials Finetune LLMA with Multiple GPUs Deploy Inference for LLMA 2 Deploy Inference for Codellama Deploy Inference for Stable Diffusion v21 Finetune Stable Diffusion model on TIR Deploy Inference for MPT7BCHAT Custom Containers in TIR Fine Tuning Bloom Natural Language Queries to SQL wth Code Llama E2E Networks documentation Other Services on E2E Networks License Management License Management Introduction The License Management in Myaccount portal is a simple and intuitive webbased user interface for managing and buying RDP MS SQL license for your Node as per your requirement Buying a license means that you designate that license for one node The designation avoids sharing a license across more than one node For example after you have assigned a license to a node you are permitted to run that licensed software on that node Refer below a detailed description of applicationsoftware licenses available for your node License Description RDP The remote desktop protocol RDP is used to access to server or application hosted on a node It allows you to connect access and control data and resources on a node as if you were doing it locally MS SQL SQL Server is a database server by Microsoft The Microsoft relational database management system is a software product that primarily stores and retrieves data requested by other applications These applications may run on the same or a different compute node Going more indepth in order to understand what a SQL Server is you must first understand what SQL is SQL is a specialpurpose programming language designed to handle data in a relational database management system A database server is a computer program that provides database services to other programs or computers as defined by the clientserver model Therefore a SQL Server is a database server that implements the Structured Query Language SQL There are many different versions of Microsoft SQL Server catering for different workloads and demands Physical Machine When running MS SQL Server in a physical OSE all physical cores on the server must be licensed A minimum of four core licenses is required for each physical processor on the server Calculate the Licenses on Physical Machines Count the total number of physical cores in the server Since the Per 2 Core licenses used in SPLA Microsoft Services Provider License Agreement you must divide the number of the available cores on the physical machine by two to determine the actual number of licenses required on the machine Note The use of hyperthreading technology does not affect the number of licenses required when running SQL Server software in a physical OSE Logic Example Lets say you have a physical server with a single Processor Case Case1 Case1 Case1 Case1 Total Processors Available 1 1 1 1 Total Cores Available 2 4 8 16 Licenses Required Per 2 Cores 2 2 4 8 Example Lets say you have a physical server with two processors Case Case2 Case2 Case2 Case2 Total Processors Available 2 2 2 2 Total Cores Available 2 4 8 16 Licenses Required Per 2 Cores 4 4 4 8 Virtual Machine Licenses Calculation Logic When running MS SQL server in virtual OSEs all the virtual core or virtual processor virtual CPU virtual thread allocated to the VM must be licensed A minimum of four core licenses is required for each VM Calculate the Licenses on Virtual Machines Count the total number of virtual cores available in a virtual machine Since the Per 2 Core licenses used in SPLA so you must divide the number of the available virtual core on the virtual machine by two to determine the actual number of licenses required on the virtual machine Example Lets say you have 2 or more virtual cores on the virtual machine VMs VM1 VM2 VM3 VM4 Total Virtual Cores Available 2 4 8 16 Licenses Required Per 2 Cores 2 2 4 8 You can refer to the microsoft official document Buy License This tutorial will show you how to buy and manage license for Myaccount Go to My Account and log in using your credentials set up at the time of creating and activating the My Account On the left Navigation bar Select License management available under the service section You will redirect to the Manage License page Click on the Buy New License Select the license type you want to buy RDP License MS SQL License After selecting a license type click on the Buy button You will be redirected to the buy license page Here need to specify the node details RDP License MS SQL License After filling the required information click the Place Order button A confirmation window will be opened Please provide your confirmation after reading the details You will redirect to the Manage License page Here you will get an information message Your request will be reviewed by E2E Networks support Team You will be notified about the request approval by email Purchased license state will change from ActivationPending to Activated Terminate Active License Go to Manage License page and select the license you want to terminate Click on the Termination Request action A confirmation window will be opened Please provide your confirmation after reading the details The license state will change from Activated to TerminationPending You will be notified about the termination request approval by email On this page Introduction Buy License RDP License MS SQL License RDP License MS SQL License Terminate Active License Products TIR AI Platform GPU Dedicated Compute CPU Intensive Cloud High Memory Cloud Linux Smart Dedicated cPanel Linux Cloud Windows Cloud Windows SQL Cloud Plesk Windows Cloud GPU Smart Dedicated Load Balancer Company About Us Meet the Team Become a Partner E2E in Media Testimonials Investors Careers Contact Us Contact Sales Escalation Matrix Service Level Agreement Terms of Service Privacy Policy Refund Policy Policy FAQ Resources Blog Events Service Health Status Help White Papers Ecosystem Enablers Customers Certifications Countries Served FAQs E2E Networks Limited E2E Networks Limited is a NSE Listed AIFirst Hyperscale Cloud Computing Platform CIN Number L72900DL2009PLC341980 Copyright 2023 E2E Networks Limited


E2E Networks Billing and Payment Information E2E Networks documentation Skip to content E2E Cloud Docs E2E Networks TIR Toggle navigation menu Login Sign Up E2E Networks documentation K Docs E2E Networks TIR Myaccount Getting Started with Myaccount SignUp Process for Indian Customers Customer validation Process for Indian Customers SignUp Process for International Customers Customer Validation Process for International Process Customer Validation Process for Contact Persons Domestic Customer Validation Process FAQs International Customer Validation Process FAQs Sign In Process Release Notes Compute Nodes Virtual Compute Nodes Monitoring 1Click Deployment Active Directory GPU GPU Cloud EQS Introduction Appliance Load Balancer Appliance Auto Scaling Introduction Concepts Define Scale Groups FaaS Function as a Service FaaS Network CDN VPC How to reserve an IP address Reserve IP Pool DNS Custom Reverse DNS Firewall Security Group Tag Security Firewall Bitninja Best Practices SSH Key Management Audit Logs Password Policy 2Factor Authentication Others License Management User Management Purchase SSL CertbotPlugin Apply or Redeem Coupon Code Account Statement Cloud Platform Support Introduction Platform Support Policy FAQ E2Es MyAccount FAQs Code of Conduct of Directors and Senior Management CSR Policy Whistle blower policy Jitsi Meet Mod Evasive Multisite using cPanel Softaculous Copying data from Linux to Windows using WinSCP Migrate MySQL Database Between DBaaS Manage MySQL Abuse Abuse Logs Abuse Attacks Spam Mails Phishing Complaint Copyright Complaint Billing Payment Payment Method EMandate Redeem Coupon Customer Details Updation Setup AutoDebit feature TDS Deduction process Declaration us 206AB Minimum Billing Provisioning and Deprovisioning Process View Invoice and Payment Prepaid Billing Set up Infra Credits Balance Alert Whatsapp notification for Payment reminder Restore Service on a Suspended Account for NonPayment Database Database Database PostgreSQL Parameter Group MongoDB mariaDB Storage Storage Block Storage Object Storage CDP Backup Scalable File System Kubernetes Kubernetes Service Kubernetes Kubernetes Marketplace Monitoring Stack Cert Manager Nginx Ingress Controller Troubleshooting Argo CD Declarative GitOps CD for Kubernetes Deploy to Kubernetes using Argo CD and GitOps Jenkins CI Tool Setup Jenkins On Kubernetes Cluster Ansible CD Tool Istio Service Connecting to Dbaas FAQS Container Registery Container Registery API Developers Guide API SDK E2E CLI Tool Introduction Terraform Terraform Getting Started e2enode Resource Node Plans e2eimage Resource AIML TIR AI Release Notes TIR AI Platform Introduction Getting Started Howto Guides Projects Notebooks Committed Notebook GPU H100 Plans Datasets Model Repository Model Endpoints Pipeline Run Scheduled Run Fine Tuning Models Model Playground Samples and Tutorials API Tokens SSH Key Container Team Features Settings Analytics Billing AIML Tutorials Finetune LLMA with Multiple GPUs Deploy Inference for LLMA 2 Deploy Inference for Codellama Deploy Inference for Stable Diffusion v21 Finetune Stable Diffusion model on TIR Deploy Inference for MPT7BCHAT Custom Containers in TIR Fine Tuning Bloom Natural Language Queries to SQL wth Code Llama E2E Networks documentation E2E Networks Billing and Payment Information E2E Networks Billing and Payment Information The Billing and Payment section of E2E Networks documentation covers crucial aspects of billing procedures payment options and financial processes This section includes detailed information on payment options for both domestic and international customers setting up autodebit features TDS deduction processes viewing invoices and payments and more Key Topics For detailed information refer to the respective sections in our documentation Payment Method Learn more about our Payment Methods EMandate Learn more about EMandate Redeem Coupon Guide on how to redeem coupons Customer Details Updation Guide on updating customer details Setup AutoDebit feature Setting up autodebit TDS Deduction process Guide on TDS deduction process Declaration us 206AB Declaration of us 206AB Minimum Billing Understand minimum billing Provisioning and Deprovisioning Process Learn about our provisioning and deprovisioning process View Invoice and Payment Learn about viewing invoice and payment details Prepaid Billing Learn about prepaid billing Set up Infra Credits Balance Alert Create alerts for infra credits balance Whatsapp notification for Payment reminder Set up whatsapp notifications for payment reminders Restore Service on a Suspended Account for NonPayment Learn how to restore service for suspended accounts On this page Key Topics Products TIR AI Platform GPU Dedicated Compute CPU Intensive Cloud High Memory Cloud Linux Smart Dedicated cPanel Linux Cloud Windows Cloud Windows SQL Cloud Plesk Windows Cloud GPU Smart Dedicated Load Balancer Company About Us Meet the Team Become a Partner E2E in Media Testimonials Investors Careers Contact Us Contact Sales Escalation Matrix Service Level Agreement Terms of Service Privacy Policy Refund Policy Policy FAQ Resources Blog Events Service Health Status Help White Papers Ecosystem Enablers Customers Certifications Countries Served FAQs E2E Networks Limited E2E Networks Limited is a NSE Listed AIFirst Hyperscale Cloud Computing Platform CIN Number L72900DL2009PLC341980 Copyright 2023 E2E Networks Limited


Deploy Inference Endpoint For MPT7BCHAT E2E Networks documentation Skip to content E2E Cloud Docs E2E Networks TIR Toggle navigation menu Login Sign Up E2E Networks documentation K Docs E2E Networks TIR Myaccount Getting Started with Myaccount SignUp Process for Indian Customers Customer validation Process for Indian Customers SignUp Process for International Customers Customer Validation Process for International Process Customer Validation Process for Contact Persons Domestic Customer Validation Process FAQs International Customer Validation Process FAQs Sign In Process Release Notes Compute Nodes Virtual Compute Nodes Monitoring 1Click Deployment Active Directory GPU GPU Cloud EQS Introduction Appliance Load Balancer Appliance Auto Scaling Introduction Concepts Define Scale Groups FaaS Function as a Service FaaS Network CDN VPC How to reserve an IP address Reserve IP Pool DNS Custom Reverse DNS Firewall Security Group Tag Security Firewall Bitninja Best Practices SSH Key Management Audit Logs Password Policy 2Factor Authentication Others License Management User Management Purchase SSL CertbotPlugin Apply or Redeem Coupon Code Account Statement Cloud Platform Support Introduction Platform Support Policy FAQ E2Es MyAccount FAQs Code of Conduct of Directors and Senior Management CSR Policy Whistle blower policy Jitsi Meet Mod Evasive Multisite using cPanel Softaculous Copying data from Linux to Windows using WinSCP Migrate MySQL Database Between DBaaS Manage MySQL Abuse Abuse Logs Abuse Attacks Spam Mails Phishing Complaint Copyright Complaint Billing Payment Payment Method EMandate Redeem Coupon Customer Details Updation Setup AutoDebit feature TDS Deduction process Declaration us 206AB Minimum Billing Provisioning and Deprovisioning Process View Invoice and Payment Prepaid Billing Set up Infra Credits Balance Alert Whatsapp notification for Payment reminder Restore Service on a Suspended Account for NonPayment Database Database Database PostgreSQL Parameter Group MongoDB mariaDB Storage Storage Block Storage Object Storage CDP Backup Scalable File System Kubernetes Kubernetes Service Kubernetes Kubernetes Marketplace Monitoring Stack Cert Manager Nginx Ingress Controller Troubleshooting Argo CD Declarative GitOps CD for Kubernetes Deploy to Kubernetes using Argo CD and GitOps Jenkins CI Tool Setup Jenkins On Kubernetes Cluster Ansible CD Tool Istio Service Connecting to Dbaas FAQS Container Registery Container Registery API Developers Guide API SDK E2E CLI Tool Introduction Terraform Terraform Getting Started e2enode Resource Node Plans e2eimage Resource AIML TIR AI Release Notes TIR AI Platform Introduction Getting Started Howto Guides Projects Notebooks Committed Notebook GPU H100 Plans Datasets Model Repository Model Endpoints Pipeline Run Scheduled Run Fine Tuning Models Model Playground Samples and Tutorials API Tokens SSH Key Container Team Features Settings Analytics Billing AIML Tutorials Finetune LLMA with Multiple GPUs Deploy Inference for LLMA 2 Deploy Inference for Codellama Deploy Inference for Stable Diffusion v21 Finetune Stable Diffusion model on TIR Deploy Inference for MPT7BCHAT Custom Containers in TIR Fine Tuning Bloom Natural Language Queries to SQL wth Code Llama E2E Networks documentation Welcome to TIR AI Platform Documentation Tutorials Deploy Inference Endpoint For MPT7BCHAT Deploy Inference Endpoint For MPT7BCHAT In this tutorial we will create a model endpoint against MPT7bchat model The tutorial will mainly focus on the following Model Endpoint creation for mpt7bchat using prebuilt container Model Endpoint creation for mpt7bchat with custom model weights Brief description about the supported parameters for image generation Creating a readytouse Model endpoint TIR platform supports a variety of model formats through prebuit containers eg pytorch triton metallma2 mosaicmpt7bchat For the scope of this tutorial we will use prebuilt container MPT7BCHAT for the model endpoint When you use prebuilt containers all you need to do is select the container and launch the endpoint API handler will be automatically created for you Steps to create endpoint Go to TIR Dashboard Go to Model Endpoints Create a new Endpoint Choose MPT7BCHAT option Pick a suitable GPU plan Complete the endpoint creation When your endpoint is ready visit the Sample API request section to test your endpoint using curl Creating Model endpoint with custom model weights To create Inference against mpt7bchat model with custom model weights we will Download mpt7bchat model from huggingface Upload the model to Model Bucket EOS Create an inference endpoint model endpoint in TIR to serve API requests Step 1 Define a model in TIR Dashboard Before we proceed with downloading or finetuning optional the model weights let us first define a model in TIR dashboard Go to TIR Dashboard Choose a project Go to Model section Click on Create Model Enter a model name of your choosing eg mpt7bchat1 Select Model Type as Custom Click on CREATE You will now see details of EOS E2E Object Storage bucket created for this model EOS Provides a S3 compatible API to upload or download content We will be using MinIO CLI in this tutorial Copy the Setup Host command from Setup Minio CLI tab to a notepad or leave it in the clipboard We will soon use it to setup MinIO CLI Note In case you forget to copy the setup host command for MinIO CLI dont worry You can always go back to model details and get it again Step 1 Define a model in TIR Dashboard Before we proceed with downloading or finetuning optional the model weights let us first define a model in TIR dashboard Go to TIR Dashboard Choose a project Go to Model section Click on Create Model Enter a model name of your choosing eg stablediffusion21 Select Model Type as Custom Click on CREATE You will now see details of EOS E2E Object Storage bucket created for this model EOS Provides a S3 compatible API to upload or download content We will be using MinIO CLI in this tutorial Copy the Setup Host command from Setup Minio CLI tab to a notepad or leave it in the clipboard We will soon use it to setup MinIO CLI Note In case you forget to copy the setup host command for MinIO CLI dont worry You can always go back to model details and get it again Step 2 Start a new Notebook To work with the model weights we will need to first download them to a local machine or a notebook instance In TIR Dashboard Go to Notebooks Launch a new Notebook with mpt7bchat image and a hardware plan eg A10080 We recommand a GPU plan if you plan to test or finetune the model Click on the Notebook name or Launch Notebook option to start jupyter labs environment In the jupyter labs Click New Launcher and Select Terminal Now paste and run the command for setting up MinIO CLI Host from Step 1 If the command works you will have mc cli ready for uploading our model Step 3 Download the mpt7bchat model from notebook Now our EOS bucket will store the model weights Let us download the weights from Hugging face Start a new notebook untitledipynb in jupyter labs Run the below commands The model will be downloaded by huggingface sdk in the HOMEcache folder import transformers import torch from transformers import AutoTokenizer model transformersAutoModelForCausalLMfrompretrained mosaicmlmpt7bchat trustremotecodeTrue tokenizer AutoTokenizerfrompretrainedEleutherAIgptneox20b pipe transformerspipeline textgeneration modelmosaicmlmpt7bchat tokenizertokenizer devicemapauto torchdtypetorchbfloat16 trustremotecodeTrue Note If you face any issues running above code in the notebook cell you may be missing required libraries This may happen if you did not launch the notebook with Transformers image In such situation you can install the required libraries below pip install transformers accelerate xformers einopsx Let us run a simple inference to test the model output pipeHere is a recipe for vegan banana breadn dosampleTrue maxnewtokens100 usecacheTrue printoutput Step 4 Upload the model to Model Bucket EOS Now that the model works as expected you can finetune it with your own data or choose to serve the model asis This tutorial assumes you are uploading the model asis to create inference endpoint In case you finetune the model you can follow similar steps to upload the model to EOS bucket go to the directory that has the huggingface model code cd HOMEcachehuggingfacehubmodelsmpt7bchat1snapshots push the contents of the folder to EOS bucket Go to TIR Dashboard Models Select your model Copy the cp command from Setup MinIO CLI tab The copy command would look like this depending your model name mc cp r MODELNAME mpt7bchat1mptbchat1b9402a here we replace MODELNAME with to upload all contents of snapshots folder mc cp r mpt7bchat1mptbchat1b9402a Note The model directory name may be a little different we assume it is modelsmpt7bchat1 In case this command does not work list the directories in the below path to identify the model directory HOMEcachehuggingfacehub Step 5 Create an endpoint for our model With model weights uploaded to TIR Models EOS Bucket what remains is to just launch the endpoint and serve API requests Head back to the section on Creating a readytouse Model endpoint above and follow the steps to create the endpoint for your model While creating the endpoint make sure you select the appropriate model in the model details subsection INFERENCE After you have successfully launched model endpoint wait for few minutes for loading the model And then you can use api request for prediction Below is the sample body of the inference request instances text heres the Recipe of pancakes params maxlength 100 This will give the below response predictions heres the Recipe of pancakes with strawberries and creamnnIngredients nn1 cup allpurpose flourn1 teaspoon baking powdern14 teaspoon saltn14 cup whole milkn14 cup buttermilkn1 tablespoon vegetable oiln12 cup sliced fresh strawberriesn12 cup whipped creamnnDirectionsnn1 Preheat a griddle or nonstick skillet over mediumhigh heat You can also pass multiple prompt texts instances text heres the tea recipe textheres the pancakes recipe params maxlength 100 This will give the below response predictions heres the tea recipenn1 Boil watern2 Steep tea bag in boiling water for 35 minutesn3 Add honey to tasten4 Servennand heres the teann1 Boil watern2 Steep tea bag in boiling water for 35 minutesn3 Add honey to tasten4 Servenn heres the pancakes recipennIngredientsnn1 cup allpurpose flourn12 cup wholewheat flourn12 cup rolled oatsn12 cup unsweetened applesaucen12 cup milkn12 cup watern12 teaspoon baking powdern12 teaspoon baking sodan12 teaspoon saltn12 teaspoon cinnamonn14 teaspoon nutmegn14 teaspoon You can pass the parameters in your request body listed below to control your output Supported parameters Parameters that control the length of the output maxlength int optional defaults to 20 The maximum length the generated tokens can have Corresponds to the length of the input prompt maxnewtokens Its effect is overridden by maxnewtokens if also set maxnewtokens int optional The maximum numbers of tokens to generate ignoring the number of tokens in the prompt minlength int optional defaults to 0 The minimum length of the sequence to be generated Corresponds to the length of the input prompt minnewtokens Its effect is overridden by minnewtokens if also set minnewtokens int optional The minimum numbers of tokens to generate ignoring the number of tokens in the prompt earlystopping bool or str optional defaults to False Controls the stopping condition for beambased methods like beamsearch It accepts the following values True where the generation stops as soon as there are numbeams complete candidates False where an heuristic is applied and the generation stops when is it very unlikely to find better candidates never where the beam search procedure only stops when there cannot be better candidates canonical beam search algorithm maxtime float optional The maximum amount of time you allow the computation to run for in seconds generation will still finish the current pass after allocated time has been passed Parameters that control the generation strategy used dosample bool optional defaults to False Whether or not to use sampling use greedy decoding otherwise numbeams int optional defaults to 1 Number of beams for beam search 1 means no beam search numbeamgroups int optional defaults to 1 Number of groups to divide numbeams into in order to ensure diversity among different groups of beams this paper for more details penaltyalpha float optional The values balance the model confidence and the degeneration penalty in contrastive search decoding usecache bool optional defaults to True Whether or not the model should use the past last keyvalues attentions if applicable to the model to speed up decoding Parameters for manipulation of the model output logits temperature float optional defaults to 10 The value used to modulate the next token probabilities topk int optional defaults to 50 The number of highest probability vocabulary tokens to keep for topkfiltering topp float optional defaults to 10 If set to float 1 only the smallest set of most probable tokens with probabilities that add up to topp or higher are kept for generation typicalp float optional defaults to 10 Local typicality measures how similar the conditional probability of predicting a target token next is to the expected conditional probability of predicting a random token next given the partial text already generated If set to float 1 the smallest set of the most locally typical tokens with probabilities that add up to typicalp or higher are kept for generation See this paper for more details epsiloncutoff float optional defaults to 00 If set to float strictly between 0 and 1 only tokens with a conditional probability greater than epsiloncutoff will be sampled In the paper suggested values range from 3e4 to 9e4 depending on the size of the model See Truncation Sampling as Language Model Desmoothing for more details etacutoff float optional defaults to 00 Eta sampling is a hybrid of locally typical sampling and epsilon sampling If set to float strictly between 0 and 1 a token is only considered if it is greater than either etacutoff or sqrtetacutoff expentropysoftmaxnexttokenlogits The latter term is intuitively the expected next token probability scaled by sqrtetacutoff In the paper suggested values range from 3e4 to 2e3 depending on the size of the model See Truncation Sampling as Language Model Desmoothing for more details diversitypenalty float optional defaults to 00 This value is subtracted from a beams score if it generates a token same as any beam from other group at a particular time Note that diversitypenalty is only effective if group beam search is enabled repetitionpenalty float optional defaults to 10 The parameter for repetition penalty 10 means no penalty See this paper for more details encoderrepetitionpenalty float optional defaults to 10 The paramater for encoderrepetitionpenalty An exponential penalty on sequences that are not in the original input 10 means no penalty lengthpenalty float optional defaults to 10 Exponential penalty to the length that is used with beambased generation It is applied as an exponent to the sequence length which in turn is used to divide the score of the sequence Since the score is the log likelihood of the sequence ie negative lengthpenalty 00 promotes longer sequences while lengthpenalty 00 encourages shorter sequences norepeatngramsize int optional defaults to 0 If set to int 0 all ngrams of that size can only occur once badwordsids ListListint optional List of list of token ids that are not allowed to be generated Check NoBadWordsLogitsProcessor for further documentation and examples forcewordsids ListListint or ListListListint optional List of token ids that must be generated If given a ListListint this is treated as a simple list of words that must be included the opposite to badwordsids If given ListListListint this triggers a disjunctive constraint where one can allow different forms of each word renormalizelogits bool optional defaults to False Whether to renormalize the logits after applying all the logits processors or warpers including the custom ones Its highly recommended to set this flag to True as the search algorithms suppose the score logits are normalized but some logit processors or warpers break the normalization constraints ListConstraint optional Custom constraints that can be added to the generation to ensure that the output will contain the use of certain tokens as defined by Constraint objects in the most sensible way possible forcedbostokenid int optional defaults to modelconfigforcedbostokenid The id of the token to force as the first generated token after the decoderstarttokenid Useful for multilingual models like mBART where the first generated token needs to be the target language token forcedeostokenid Unionint Listint optional defaults to modelconfigforcedeostokenid The id of the token to force as the last generated token when maxlength is reached Optionally use a list to set multiple endofsequence tokens removeinvalidvalues bool optional defaults to modelconfigremoveinvalidvalues Whether to remove possible nan and inf outputs of the model to prevent the generation method to crash Note that using removeinvalidvalues can slow down generation exponentialdecaylengthpenalty tupleint float optional This Tuple adds an exponentially increasing length penalty after a certain amount of tokens have been generated The tuple shall consist of startindex decayfactor where startindex indicates where penalty starts and decayfactor represents the factor of exponential decay suppresstokens Listint optional A list of tokens that will be suppressed at generation The SupressTokens logit processor will set their log probs to inf so that they are not sampled beginsuppresstokens Listint optional A list of tokens that will be suppressed at the beginning of the generation The SupressBeginTokens logit processor will set their log probs to inf so that they are not sampled forceddecoderids ListListint optional A list of pairs of integers which indicates a mapping from generation indices to token indices that will be forced before sampling For example 1 123 means the second generated token will always be a token of index 123 sequencebias DictTupleint float optional Dictionary that maps a sequence of tokens to its bias term Positive biases increase the odds of the sequence being selected while negative biases do the opposite Check SequenceBiasLogitsProcessor for further documentation and examples guidancescale float optional The guidance scale for classifier free guidance CFG CFG is enabled by setting guidancescale 1 Higher guidance scale encourages the model to generate samples that are more closely linked to the input prompt usually at the expense of poorer quality lowmemory bool optional Switch to sequential topk for contrastive search to reduce peak memory Used with contrastive search Parameters that define the output variables of generate numreturnsequences int optional defaults to 1 The number of independently computed returned sequences for each element in the batch outputattentions bool optional defaults to False Whether or not to return the attentions tensors of all attention layers See attentions under returned tensors for more details outputhiddenstates bool optional defaults to False Whether or not to return the hidden states of all layers See hiddenstates under returned tensors for more details outputscores bool optional defaults to False Whether or not to return the prediction scores See scores under returned tensors for more details returndictingenerate bool optional defaults to False Whether or not to return a ModelOutput instead of a plain tuple Special tokens that can be used at generation time padtokenid int optional The id of the padding token bostokenid int optional The id of the beginningofsequence token eostokenid Unionint Listint optional The id of the endofsequence token Optionally use a list to set multiple endofsequence tokens Generation parameters exclusive to encoderdecoder models encodernorepeatngramsize int optional defaults to 0 If set to int 0 all ngrams of that size that occur in the encoderinputids cannot occur in the decoderinputids decoderstarttokenid int optional If an encoderdecoder model starts decoding with a different token than bos the id of that token On this page Creating a readytouse Model endpoint Creating Model endpoint with custom model weights INFERENCE Supported parameters Products TIR AI Platform GPU Dedicated Compute CPU Intensive Cloud High Memory Cloud Linux Smart Dedicated cPanel Linux Cloud Windows Cloud Windows SQL Cloud Plesk Windows Cloud GPU Smart Dedicated Load Balancer Company About Us Meet the Team Become a Partner E2E in Media Testimonials Investors Careers Contact Us Contact Sales Escalation Matrix Service Level Agreement Terms of Service Privacy Policy Refund Policy Policy FAQ Resources Blog Events Service Health Status Help White Papers Ecosystem Enablers Customers Certifications Countries Served FAQs E2E Networks Limited E2E Networks Limited is a NSE Listed AIFirst Hyperscale Cloud Computing Platform CIN Number L72900DL2009PLC341980 Copyright 2023 E2E Networks Limited


Security Groups E2E Networks documentation Skip to content E2E Cloud Docs E2E Networks TIR Toggle navigation menu Login Sign Up E2E Networks documentation K Docs E2E Networks TIR Myaccount Getting Started with Myaccount SignUp Process for Indian Customers Customer validation Process for Indian Customers SignUp Process for International Customers Customer Validation Process for International Process Customer Validation Process for Contact Persons Domestic Customer Validation Process FAQs International Customer Validation Process FAQs Sign In Process Release Notes Compute Nodes Virtual Compute Nodes Monitoring 1Click Deployment Active Directory GPU GPU Cloud EQS Introduction How to Create EQS Actions Add Queue under tab Actions for queue service Using SDK Appliance Load Balancer Appliance Auto Scaling Introduction Concepts Define Scale Groups FaaS Function as a Service FaaS How to Create Functions Functions Information Network CDN VPC How to reserve an IP address Reserve IP Pool DNS Custom Reverse DNS Firewall Security Group Tag Security Firewall Bitninja Best Practices SSH Key Management Audit Logs Password Policy 2Factor Authentication Others License Management User Management Purchase SSL CertbotPlugin Apply or Redeem Coupon Code Account Statement Cloud Platform Support Introduction Platform Support Policy FAQ E2Es MyAccount FAQs Code of Conduct of Directors and Senior Management CSR Policy Whistle blower policy Jitsi Meet Mod Evasive Multisite using cPanel Softaculous Copying data from Linux to Windows using WinSCP Migrate MySQL Database Between DBaaS Manage MySQL Abuse Abuse Logs Abuse Attacks Spam Mails Phishing Complaint Copyright Complaint Billing Payment Payment Method EMandate Redeem Coupon Customer Details Updation Setup AutoDebit feature TDS Deduction process Declaration us 206AB Minimum Billing Provisioning and Deprovisioning Process View Invoice and Payment Prepaid Billing Set up Infra Credits Balance Alert Whatsapp notification for Payment reminder Restore Service on a Suspended Account for NonPayment Database Database Database PostgreSQL Parameter Group How to create Parameter Group MongoDB mariaDB Storage Storage Block Storage Object Storage CDP Backup Scalable File System Kubernetes Kubernetes Service Kubernetes Kubernetes Marketplace Monitoring Stack Cert Manager Nginx Ingress Controller Troubleshooting Argo CD Declarative GitOps CD for Kubernetes Deploy to Kubernetes using Argo CD and GitOps Jenkins CI Tool Setup Jenkins On Kubernetes Cluster Ansible CD Tool Istio Service Connecting to Dbaas FAQS Container Registery Container Registry Simplifying Pull Operations with UserFriendly Interface API Developers Guide API SDK E2E CLI Tool Introduction Terraform Terraform Getting Started e2enode Resource Node Plans e2eimage Resource AIML TIR AI Release Notes TIR AI Platform Introduction Getting Started Howto Guides Projects Notebooks Committed Notebook GPU H100 Plans Datasets Model Repository Model Endpoints Pipeline Run Scheduled Run Fine Tuning Models Model Playground Samples and Tutorials API Tokens SSH Key Container Team Features Settings Analytics Billing AIML Tutorials Finetune LLMA with Multiple GPUs Deploy Inference for LLMA 2 Deploy Inference for Codellama Deploy Inference for Stable Diffusion v21 Finetune Stable Diffusion model on TIR Deploy Inference for MPT7BCHAT Custom Containers in TIR Fine Tuning Bloom Natural Language Queries to SQL wth Code Llama E2E Networks documentation Networking on E2E Cloud Security Groups Security Groups Introduction An E2E Networks Security Group acts as a virtual firewall for your Server Node to control incoming and outgoing traffic Both inbound and outbound rules control the flow of traffic to and traffic from your Server Node respectively Navigate to Security Groups page Please go to MyAccount and log in using your credentials set up at the time of creating and activating the E2E Networks MyAccount After you log in to the E2E Networks MyAccount On the left side of the MyAccount dashboard click on the Security Groups submenu available under the Network section You will be directed to the Manage Security Groups page Working with Security Groups The following sections describe how you can use Security Group Create New Security Group Click on the Security Groups submenu available under the Network section You will be directed to the Manage Security Groups page Click on the Create Security Groups button Click on the Create Security Groups button The Create Security Groups page will appear Inbound Rules When you create a security group it has no inbound rules No inbound traffic originating from another host to your instance is allowed until you add inbound rules to the security group Outbound Rules By default a security group includes an outbound rule that allows all outbound traffic We recommend that you remove this default rule and add outbound rules that allow specific outbound traffic only Name The name for the security group for example my securitygroup A name can be up to 128 characters in length Allowed characters are az AZ When the name contains trailing spaces we trim the spaces when we save the name For example if you enter Test Security Group for the name we store it as Test Security Group Protocol The protocol to allow The most common protocols are 6 TCP 17 UDP and 1 ICMP Port range For TCP UDP or a custom protocol the range of ports to allow You can specify a single port number for example 22808080 ICMP type and code For ICMP the ICMP type and code For example use type 8 for ICMP Echo Request or type 128 for ICMPv6 Echo Request Click on the Create Security Groups button Click on the Create group button then after the new Security Group is created and redirected to the Manage Security Groups page Security Groups Actions Click on the Actions button list out Delete button Click on the Delete button and confirm the same in the pop up menu to delete the chosen Security Group Click on the Actions button list out Make Group default button Click on the Make Group default button to make default security group Associated Node With Security Group Click on the Associated node Details tab to associate a Node Click on the Click Here link to associate a Node Its redirect to Manage Node Page Click on the Security Group tab to associate the security group with Node Note By default at least one security group is attached to the node Click on the Attach Security Group button to attach multiple security groups with Node Click on the button and attach multiple security groups After attaching security groups with Node visible in the Security Groups tab Click on the Detach button to detach the security group from node but at least one Security Group attaches with node Allow All Traffic If you choose to allow all traffic in a security group it means that all inbound and outbound network traffic will be permitted to and from the resources associated with that security group Here is a description of what allowing all traffic entails Inbound Traffic All incoming network traffic from any source IP address IP range or specific IP address will be allowed All protocols eg TCP UDP ICMP and port ranges will be permitted for incoming connections This includes traffic intended for services applications or any other protocol running on your resources Outbound Traffic All outgoing network traffic from your resources will be allowed to any destination IP address IP range or specific IP address All protocols eg TCP UDP ICMP and port ranges will be permitted for outgoing connections This includes traffic generated by your resources such as requests to external services database connections or any other outbound communication Click on the Allow All Traffic button to add new security group Associated Node Actions Click on the Actions button list out View Details button Click on View Details user can redirect to Manage Node list and can see node details Adding Node Click on the Compute Submenu under Products Click on the Add New Node and redirect to the Create Compute Node page Select any plan and click on Create button then redirect to Create Compute Node page Select Security Group under the Node Security section while creating nodes On this page Introduction Navigate to Security Groups page Working with Security Groups Create New Security Group Inbound Rules Outbound Rules Security Groups Actions Associated Node With Security Group Allow All Traffic Associated Node Actions Adding Node Products TIR AI Platform GPU Dedicated Compute CPU Intensive Cloud High Memory Cloud Linux Smart Dedicated cPanel Linux Cloud Windows Cloud Windows SQL Cloud Plesk Windows Cloud GPU Smart Dedicated Load Balancer Company About Us Meet the Team Become a Partner E2E in Media Testimonials Investors Careers Contact Us Contact Sales Escalation Matrix Service Level Agreement Terms of Service Privacy Policy Refund Policy Policy FAQ Resources Blog Events Service Health Status Help White Papers Ecosystem Enablers Customers Certifications Countries Served FAQs E2E Networks Limited E2E Networks Limited is a NSE Listed AIFirst Hyperscale Cloud Computing Platform CIN Number L72900DL2009PLC341980 Copyright 2023 E2E Networks Limited


Introduction E2E Networks documentation Skip to content E2E Cloud Docs E2E Networks TIR Toggle navigation menu Login Sign Up E2E Networks documentation K Docs E2E Networks TIR Myaccount Getting Started with Myaccount SignUp Process for Indian Customers Customer validation Process for Indian Customers SignUp Process for International Customers Customer Validation Process for International Process Customer Validation Process for Contact Persons Domestic Customer Validation Process FAQs International Customer Validation Process FAQs Sign In Process Release Notes Compute Nodes Virtual Compute Nodes Monitoring 1Click Deployment Active Directory GPU GPU Cloud EQS Introduction How to Create EQS Actions Add Queue under tab Actions for queue service Using SDK Appliance Load Balancer Appliance Auto Scaling Introduction Concepts Define Scale Groups FaaS Function as a Service FaaS How to Create Functions Functions Information Network CDN VPC How to reserve an IP address Reserve IP Pool DNS Custom Reverse DNS Firewall Security Group Tag Security Firewall Bitninja Best Practices SSH Key Management Audit Logs Password Policy 2Factor Authentication Others License Management User Management Purchase SSL CertbotPlugin Apply or Redeem Coupon Code Account Statement Cloud Platform Support Introduction Platform Support Policy FAQ E2Es MyAccount FAQs Code of Conduct of Directors and Senior Management CSR Policy Whistle blower policy Jitsi Meet Mod Evasive Multisite using cPanel Softaculous Copying data from Linux to Windows using WinSCP Migrate MySQL Database Between DBaaS Manage MySQL Abuse Abuse Logs Abuse Attacks Spam Mails Phishing Complaint Copyright Complaint Billing Payment Payment Method EMandate Redeem Coupon Customer Details Updation Setup AutoDebit feature TDS Deduction process Declaration us 206AB Minimum Billing Provisioning and Deprovisioning Process View Invoice and Payment Prepaid Billing Set up Infra Credits Balance Alert Whatsapp notification for Payment reminder Restore Service on a Suspended Account for NonPayment Database Database Database PostgreSQL Parameter Group How to create Parameter Group MongoDB mariaDB Storage Storage Block Storage Object Storage CDP Backup Scalable File System Kubernetes Kubernetes Service Kubernetes Kubernetes Marketplace Monitoring Stack Cert Manager Nginx Ingress Controller Troubleshooting Argo CD Declarative GitOps CD for Kubernetes Deploy to Kubernetes using Argo CD and GitOps Jenkins CI Tool Setup Jenkins On Kubernetes Cluster Ansible CD Tool Istio Service Connecting to Dbaas FAQS Container Registery Container Registry Simplifying Pull Operations with UserFriendly Interface API Developers Guide API SDK E2E CLI Tool Introduction Terraform Terraform Getting Started e2enode Resource Node Plans e2eimage Resource AIML TIR AI Release Notes TIR AI Platform Introduction Getting Started Howto Guides Projects Notebooks Committed Notebook GPU H100 Plans Datasets Model Repository Model Endpoints Pipeline Run Scheduled Run Fine Tuning Models Model Playground Samples and Tutorials API Tokens SSH Key Container Team Features Settings Analytics Billing AIML Tutorials Finetune LLMA with Multiple GPUs Deploy Inference for LLMA 2 Deploy Inference for Codellama Deploy Inference for Stable Diffusion v21 Finetune Stable Diffusion model on TIR Deploy Inference for MPT7BCHAT Custom Containers in TIR Fine Tuning Bloom Natural Language Queries to SQL wth Code Llama E2E Networks documentation Other Services on E2E Networks Introduction Introduction This feature is provided in order to get in touch with our 24x7 support team whenever required You can create and track support tickets using this page As of now we have 2 categories Cloud Platform For all technical support related to the cloud services Billing Billing and Payment related queries select Billing type tickets Platform Support To access the ticketing portal click on the Platform Support on top You will be redirected to the Platform Support page To create a new ticket click on the Create Platform Support Ticket button You will be redirected to the New Platform Support Ticket page where you can fill the required information Type Choose the respective category of ticket created Subject It can be a tagline for the reported issue Description Please share the issue observed in detail with information like server IP domain name etc and attach the relevant screenshot which can represent the issue Click on the Submit Ticket button and a new platform support ticket will be created The created ticket will be displayed like below and our team will check and reply on the same shortly You can further continue the conversation with our team using the reply button You can fill in the message and also add up attachments as required then select Reply Once the reported issue has been resolved you can close the ticket using the Actions Close button You can submit the closure reply feedback or further comments on the same and then click Close thereby closing the ticket On this page Platform Support Products TIR AI Platform GPU Dedicated Compute CPU Intensive Cloud High Memory Cloud Linux Smart Dedicated cPanel Linux Cloud Windows Cloud Windows SQL Cloud Plesk Windows Cloud GPU Smart Dedicated Load Balancer Company About Us Meet the Team Become a Partner E2E in Media Testimonials Investors Careers Contact Us Contact Sales Escalation Matrix Service Level Agreement Terms of Service Privacy Policy Refund Policy Policy FAQ Resources Blog Events Service Health Status Help White Papers Ecosystem Enablers Customers Certifications Countries Served FAQs E2E Networks Limited E2E Networks Limited is a NSE Listed AIFirst Hyperscale Cloud Computing Platform CIN Number L72900DL2009PLC341980 Copyright 2023 E2E Networks Limited


Database Management in E2E Networks E2E Networks documentation Skip to content E2E Cloud Docs E2E Networks TIR Toggle navigation menu Login Sign Up E2E Networks documentation K Docs E2E Networks TIR Myaccount Getting Started with Myaccount SignUp Process for Indian Customers Customer validation Process for Indian Customers SignUp Process for International Customers Customer Validation Process for International Process Customer Validation Process for Contact Persons Domestic Customer Validation Process FAQs International Customer Validation Process FAQs Sign In Process Release Notes Compute Nodes Virtual Compute Nodes Monitoring 1Click Deployment Active Directory GPU GPU Cloud EQS Introduction Appliance Load Balancer Appliance Auto Scaling Introduction Concepts Define Scale Groups FaaS Function as a Service FaaS Network CDN VPC How to reserve an IP address Reserve IP Pool DNS Custom Reverse DNS Firewall Security Group Tag Security Firewall Bitninja Best Practices SSH Key Management Audit Logs Password Policy 2Factor Authentication Others License Management User Management Purchase SSL CertbotPlugin Apply or Redeem Coupon Code Account Statement Cloud Platform Support Introduction Platform Support Policy FAQ E2Es MyAccount FAQs Code of Conduct of Directors and Senior Management CSR Policy Whistle blower policy Jitsi Meet Mod Evasive Multisite using cPanel Softaculous Copying data from Linux to Windows using WinSCP Migrate MySQL Database Between DBaaS Manage MySQL Abuse Abuse Logs Abuse Attacks Spam Mails Phishing Complaint Copyright Complaint Billing Payment Payment Method EMandate Redeem Coupon Customer Details Updation Setup AutoDebit feature TDS Deduction process Declaration us 206AB Minimum Billing Provisioning and Deprovisioning Process View Invoice and Payment Prepaid Billing Set up Infra Credits Balance Alert Whatsapp notification for Payment reminder Restore Service on a Suspended Account for NonPayment Database Database Database PostgreSQL Parameter Group MongoDB mariaDB Storage Storage Block Storage Object Storage CDP Backup Scalable File System Kubernetes Kubernetes Service Kubernetes Kubernetes Marketplace Monitoring Stack Cert Manager Nginx Ingress Controller Troubleshooting Argo CD Declarative GitOps CD for Kubernetes Deploy to Kubernetes using Argo CD and GitOps Jenkins CI Tool Setup Jenkins On Kubernetes Cluster Ansible CD Tool Istio Service Connecting to Dbaas FAQS Container Registery Container Registery API Developers Guide API SDK E2E CLI Tool Introduction Terraform Terraform Getting Started e2enode Resource Node Plans e2eimage Resource AIML TIR AI Release Notes TIR AI Platform Introduction Getting Started Howto Guides Projects Notebooks Committed Notebook GPU H100 Plans Datasets Model Repository Model Endpoints Pipeline Run Scheduled Run Fine Tuning Models Model Playground Samples and Tutorials API Tokens SSH Key Container Team Features Settings Analytics Billing AIML Tutorials Finetune LLMA with Multiple GPUs Deploy Inference for LLMA 2 Deploy Inference for Codellama Deploy Inference for Stable Diffusion v21 Finetune Stable Diffusion model on TIR Deploy Inference for MPT7BCHAT Custom Containers in TIR Fine Tuning Bloom Natural Language Queries to SQL wth Code Llama E2E Networks documentation Database Management in E2E Networks Database Management in E2E Networks This section of our documentation explains database management or our DBaaS offering and has details on creation configuration and maintenance of databases Our service focuses on providing scalable secure and efficient database infrastructure tailored to be highly performant Key Topics The following sections explain each aspect of database management on E2E Cloud and tips to squeeze the best performance out of it It also contains guidelines on security and backup strategies Introduction to Database Management Benefits of Efficient Database Administration Steps for Creating and Managing Database Clusters Security and Backup Strategies Specific Guidelines for PostgreSQL Specific Guidelines for mongoDB Specific Guidelines for MariaDB E2Es Database Service is designed for performance and scale Get started here On this page Key Topics Products TIR AI Platform GPU Dedicated Compute CPU Intensive Cloud High Memory Cloud Linux Smart Dedicated cPanel Linux Cloud Windows Cloud Windows SQL Cloud Plesk Windows Cloud GPU Smart Dedicated Load Balancer Company About Us Meet the Team Become a Partner E2E in Media Testimonials Investors Careers Contact Us Contact Sales Escalation Matrix Service Level Agreement Terms of Service Privacy Policy Refund Policy Policy FAQ Resources Blog Events Service Health Status Help White Papers Ecosystem Enablers Customers Certifications Countries Served FAQs E2E Networks Limited E2E Networks Limited is a NSE Listed AIFirst Hyperscale Cloud Computing Platform CIN Number L72900DL2009PLC341980 Copyright 2023 E2E Networks Limited


Sign In Process E2E Networks documentation Skip to content E2E Cloud Docs E2E Networks TIR Toggle navigation menu Login Sign Up E2E Networks documentation K Docs E2E Networks TIR Myaccount Getting Started with Myaccount SignUp Process for Indian Customers Customer validation Process for Indian Customers SignUp Process for International Customers Customer Validation Process for International Process Customer Validation Process for Contact Persons Domestic Customer Validation Process FAQs International Customer Validation Process FAQs Sign In Process Release Notes Compute Nodes Virtual Compute Nodes Monitoring 1Click Deployment Active Directory GPU GPU Cloud EQS Introduction How to Create EQS Actions Add Queue under tab Actions for queue service Using SDK Appliance Load Balancer Appliance Auto Scaling Introduction Concepts Define Scale Groups FaaS Function as a Service FaaS How to Create Functions Functions Information Network CDN VPC How to reserve an IP address Reserve IP Pool DNS Custom Reverse DNS Firewall Security Group Tag Security Firewall Bitninja Best Practices SSH Key Management Audit Logs Password Policy 2Factor Authentication Others License Management User Management Purchase SSL CertbotPlugin Apply or Redeem Coupon Code Account Statement Cloud Platform Support Introduction Platform Support Policy FAQ E2Es MyAccount FAQs Code of Conduct of Directors and Senior Management CSR Policy Whistle blower policy Jitsi Meet Mod Evasive Multisite using cPanel Softaculous Copying data from Linux to Windows using WinSCP Migrate MySQL Database Between DBaaS Manage MySQL Abuse Abuse Logs Abuse Attacks Spam Mails Phishing Complaint Copyright Complaint Billing Payment Payment Method EMandate Redeem Coupon Customer Details Updation Setup AutoDebit feature TDS Deduction process Declaration us 206AB Minimum Billing Provisioning and Deprovisioning Process View Invoice and Payment Prepaid Billing Set up Infra Credits Balance Alert Whatsapp notification for Payment reminder Restore Service on a Suspended Account for NonPayment Database Database Database PostgreSQL Parameter Group How to create Parameter Group MongoDB mariaDB Storage Storage Block Storage Object Storage CDP Backup Scalable File System Kubernetes Kubernetes Service Kubernetes Kubernetes Marketplace Monitoring Stack Cert Manager Nginx Ingress Controller Troubleshooting Argo CD Declarative GitOps CD for Kubernetes Deploy to Kubernetes using Argo CD and GitOps Jenkins CI Tool Setup Jenkins On Kubernetes Cluster Ansible CD Tool Istio Service Connecting to Dbaas FAQS Container Registery Container Registry Simplifying Pull Operations with UserFriendly Interface API Developers Guide API SDK E2E CLI Tool Introduction Terraform Terraform Getting Started e2enode Resource Node Plans e2eimage Resource AIML TIR AI Release Notes TIR AI Platform Introduction Getting Started Howto Guides Projects Notebooks Committed Notebook GPU H100 Plans Datasets Model Repository Model Endpoints Pipeline Run Scheduled Run Fine Tuning Models Model Playground Samples and Tutorials API Tokens SSH Key Container Team Features Settings Analytics Billing AIML Tutorials Finetune LLMA with Multiple GPUs Deploy Inference for LLMA 2 Deploy Inference for Codellama Deploy Inference for Stable Diffusion v21 Finetune Stable Diffusion model on TIR Deploy Inference for MPT7BCHAT Custom Containers in TIR Fine Tuning Bloom Natural Language Queries to SQL wth Code Llama E2E Networks documentation SignUp Process and Myaccount Dashboard Access Sign In Process Sign In Process The customer SignIn with multiple ways in Myaccount of E2E SignIn with credentials SignIn with Google SignIn with GitHub SignIn without Trust the device To sign in normally just put in your email and password and then click the SignIn button If you sign in without trusting the device your session will expire after 15 minutes of inactivity But if you are actively using it you wont be logged out Once you have successfully signed in you will be redirected to the dashboard SignIn with Trust the device If you SignIn with trusting the device your session will expire after 60 days However you can choose to log out manually if you want to end it before that SignIn with Google using Trust the device If you want to SignIn with Google you have to click on SignIn with Google After clicking you will be redirected to Choose an account page Enter your password and click on Next button Click on continue button You will be redirected to below page After a few seconds youll go to the 2Factor Authentication page There enter the OTP sent to your registered number and click the Validate OTP button After logging in with Google successfully you will see the dashboard A popup will appear asking if you want to trust the device If you dont click Trust the device youll be logged out automatically after 15 minutes of inactivity But if you do click Trust the device you will stay logged in with the account for 60 days SignIn with GitHub using Trust the device If you want to SignIn with GitHub you have to click on SignIn with GitHub After clicking you will be redirected to Sign in to GitHub to continue to E2E Networks Limited GitHub Integration page After a few seconds you will go to the 2Factor Authentication page There enter the OTP sent to your registered number and click the Validate OTP button After logging in with GitHub successfully you will see the dashboard A popup will appear asking if you want to trust the device If you dont click Trust the device youll be logged out automatically after 15 minutes of inactivity But if you do click Trust the device you will stay logged in with the account for 60 days On this page SignIn without Trust the device SignIn with Trust the device SignIn with Google using Trust the device SignIn with GitHub using Trust the device Products TIR AI Platform GPU Dedicated Compute CPU Intensive Cloud High Memory Cloud Linux Smart Dedicated cPanel Linux Cloud Windows Cloud Windows SQL Cloud Plesk Windows Cloud GPU Smart Dedicated Load Balancer Company About Us Meet the Team Become a Partner E2E in Media Testimonials Investors Careers Contact Us Contact Sales Escalation Matrix Service Level Agreement Terms of Service Privacy Policy Refund Policy Policy FAQ Resources Blog Events Service Health Status Help White Papers Ecosystem Enablers Customers Certifications Countries Served FAQs E2E Networks Limited E2E Networks Limited is a NSE Listed AIFirst Hyperscale Cloud Computing Platform CIN Number L72900DL2009PLC341980 Copyright 2023 E2E Networks Limited


Welcome to E2E FaaS documentation E2E Networks documentation Skip to content E2E Cloud Docs E2E Networks TIR Toggle navigation menu Login Sign Up E2E Networks documentation K Docs E2E Networks TIR Myaccount Getting Started with Myaccount SignUp Process for Indian Customers Customer validation Process for Indian Customers SignUp Process for International Customers Customer Validation Process for International Process Customer Validation Process for Contact Persons Domestic Customer Validation Process FAQs International Customer Validation Process FAQs Sign In Process Release Notes Compute Nodes Virtual Compute Nodes Monitoring 1Click Deployment Active Directory GPU GPU Cloud EQS Introduction Appliance Load Balancer Appliance Auto Scaling Introduction Concepts Define Scale Groups FaaS Function as a Service FaaS Network CDN VPC How to reserve an IP address Reserve IP Pool DNS Custom Reverse DNS Firewall Security Group Tag Security Firewall Bitninja Best Practices SSH Key Management Audit Logs Password Policy 2Factor Authentication Others License Management User Management Purchase SSL CertbotPlugin Apply or Redeem Coupon Code Account Statement Cloud Platform Support Introduction Platform Support Policy FAQ E2Es MyAccount FAQs Code of Conduct of Directors and Senior Management CSR Policy Whistle blower policy Jitsi Meet Mod Evasive Multisite using cPanel Softaculous Copying data from Linux to Windows using WinSCP Migrate MySQL Database Between DBaaS Manage MySQL Abuse Abuse Logs Abuse Attacks Spam Mails Phishing Complaint Copyright Complaint Billing Payment Payment Method EMandate Redeem Coupon Customer Details Updation Setup AutoDebit feature TDS Deduction process Declaration us 206AB Minimum Billing Provisioning and Deprovisioning Process View Invoice and Payment Prepaid Billing Set up Infra Credits Balance Alert Whatsapp notification for Payment reminder Restore Service on a Suspended Account for NonPayment Database Database Database PostgreSQL Parameter Group MongoDB mariaDB Storage Storage Block Storage Object Storage CDP Backup Scalable File System Kubernetes Kubernetes Service Kubernetes Kubernetes Marketplace Monitoring Stack Cert Manager Nginx Ingress Controller Troubleshooting Argo CD Declarative GitOps CD for Kubernetes Deploy to Kubernetes using Argo CD and GitOps Jenkins CI Tool Setup Jenkins On Kubernetes Cluster Ansible CD Tool Istio Service Connecting to Dbaas FAQS Container Registery Container Registery API Developers Guide API SDK E2E CLI Tool Introduction Terraform Terraform Getting Started e2enode Resource Node Plans e2eimage Resource AIML TIR AI Release Notes TIR AI Platform Introduction Getting Started Howto Guides Projects Notebooks Committed Notebook GPU H100 Plans Datasets Model Repository Model Endpoints Pipeline Run Scheduled Run Fine Tuning Models Model Playground Samples and Tutorials API Tokens SSH Key Container Team Features Settings Analytics Billing AIML Tutorials Finetune LLMA with Multiple GPUs Deploy Inference for LLMA 2 Deploy Inference for Codellama Deploy Inference for Stable Diffusion v21 Finetune Stable Diffusion model on TIR Deploy Inference for MPT7BCHAT Custom Containers in TIR Fine Tuning Bloom Natural Language Queries to SQL wth Code Llama E2E Networks documentation Welcome to E2E FaaS documentation Welcome to E2E FaaS documentation Contents Function as a Service FaaS Introduction How to Create Functions Functions Information Products TIR AI Platform GPU Dedicated Compute CPU Intensive Cloud High Memory Cloud Linux Smart Dedicated cPanel Linux Cloud Windows Cloud Windows SQL Cloud Plesk Windows Cloud GPU Smart Dedicated Load Balancer Company About Us Meet the Team Become a Partner E2E in Media Testimonials Investors Careers Contact Us Contact Sales Escalation Matrix Service Level Agreement Terms of Service Privacy Policy Refund Policy Policy FAQ Resources Blog Events Service Health Status Help White Papers Ecosystem Enablers Customers Certifications Countries Served FAQs E2E Networks Limited E2E Networks Limited is a NSE Listed AIFirst Hyperscale Cloud Computing Platform CIN Number L72900DL2009PLC341980 Copyright 2023 E2E Networks Limited