Chatbot APP for Data Center Orchestration
Budget: ₹1,500 – ₹12,500 INR
This is a python based application which works like a chatbot for the user. This application takes user input and interacts with a Data-Center orchestrator called ACI to configure and return object's status on the orchestrator. The orchestrator has exposed APIs and the application generates a Terraform code to create objects in the orchestrator. The values for this Terraform code has to be passed by this application taking partial input from user.
Access to ACI and exposed APIs is restricted, however API documentation can be provided. Terraform skeleton code is provided. The application has to pass the object name and number of times the object is instantiated as a key-value pair and complete the Terraform code.
The following is the expected outcomes:
1. The chatbot application should be able to perform general conversation with the user.
2. The chatbot should save the user input in a file (txt or xls) and should scan for keywords.
3. The keyword is provided, if identified in the input file, then the number of times the keyword has to be called should be identified. For example, if user inputs - "Create 50 vlans starting from vlan id 200" - In this statement, vlan is the keyword, 50 is the number of times vlan has to be created, and 200 is the the start id of that object, and 249 is the end id of the object. Here keyword to object mapping is 1:1. The number of times the object is called, and the id of the object has to be sent as key value pair.
4. A pre-defined set of Terraform codes are created. Based on the user input, the number of times the terraform code is called, and the id for that object is determined.
5. Final terraform code is constructed, and sent to user for verification. Post approval, the TF code is pushed to the orchestrator.
End to end development of the application is required. Time line is 45 days.
Access to ACI and exposed APIs is restricted, however API documentation can be provided. Terraform skeleton code is provided. The application has to pass the object name and number of times the object is instantiated as a key-value pair and complete the Terraform code.
The following is the expected outcomes:
1. The chatbot application should be able to perform general conversation with the user.
2. The chatbot should save the user input in a file (txt or xls) and should scan for keywords.
3. The keyword is provided, if identified in the input file, then the number of times the keyword has to be called should be identified. For example, if user inputs - "Create 50 vlans starting from vlan id 200" - In this statement, vlan is the keyword, 50 is the number of times vlan has to be created, and 200 is the the start id of that object, and 249 is the end id of the object. Here keyword to object mapping is 1:1. The number of times the object is called, and the id of the object has to be sent as key value pair.
4. A pre-defined set of Terraform codes are created. Based on the user input, the number of times the terraform code is called, and the id for that object is determined.
5. Final terraform code is constructed, and sent to user for verification. Post approval, the TF code is pushed to the orchestrator.
End to end development of the application is required. Time line is 45 days.