Has anyone successfully setup two-factor-authentication on Ansible-Tower?
I’m new to Ansible Tower and need to set it up with two factor authentication.
Related
Ive been following the documentation (https://cloud.google.com/endpoints/docs/openapi/get-started-cloud-run#configure_esp)
I am able to load an image (Hello example), create endpoints, and run it as a service.....however, whenever I follow the process to migrate the working services to ESPv2, I get the following:
{"message":"upstream request timeout","code":504}
I've tried this on two different services. Any thoughts/ideas?
Thanks,
Steve
I have solved this issue. I was not aware that ESPv2 is only a proxy that needs to co-exist and point to the original backend service.
As soon as I created a separate service, everything worked.
I'm trying to create multiple projects inside my Organisation. My use case is:
1. I want to make an API call that creates a new project.
2. I want to create a new DialogFlow agent (chatbot).
Dialogflow API looks pretty straightforward. Since it's backend implementation, I am using service accounts to achieve this.
My problem is that when I'm trying to create a service account, it is always scoped to some project. I spent the whole day trying to give that service account all the access that I could find, but it's still giving me a Forbidden error.
Can someone explain to me if this is possible and if so - how should I configure it through the Cloud Console so that I can end up with a service account that creates projects (that can be scoped to some folder/project if it makes it easier)?
If the answer is yes - can I create multiple chatbots in one project? And what type of permissions do I need to achieve that?
Thanks!
I was using elastic search 1.5 and now needs to migrate to 5.5. However there's no direct way supported by AWS. I'm using cloudwatch streaming support for elastic search to feed events.
Now only the new events get feed in to elastic search. I'm thinking of following steps to migrate.
Create a new ES domain with 5.5.
Do a onetime import of existing cloudwatch logs.
Change the ES domain endpoint in the lambda function to point to the new ES domain.
Drop the old ES domain.
Is there a way to achieve step 2 in the process? Or is there any better way of achieving this migration?
Your strategy looks good to me. We have done this ES migration in past. Only thing you need to remember is that 1.5 to 5.5 is not a straight forward migration. There are lots of code changes also involved. Lots of classes are not even available in 5.5.
For import; you might have to write a custom export and importer.
We have made several API's with the zend framework but due to large data amount we have to use AWS Elasticcache
There is two types of services available Redis and Mem-cached
Mem-cached is suitable for my api but i have did the several research on it for php integration
also i m so new to this environment also so i never got appropriate answer from web
So please help me to understand the Flow of Working with AWS ElasticCache Mem-cached
-> from where we can start
-> what Resource needed ?
-> what are the things we have to download and install
-> and to implement in Existing API url what are the things we need to change and do a code (From where we can start)
I'm working on web app and i want to migrate this web app to virtual machine scale set in windows azure cloud,i'm new to cloud computing ,till i didn't got any proper tutorial about virtual machine scale set,please someone help with this
A few things to consider..
You could build a custom VM which contains the complete app, or you could use VM extensions to deploy the app on a platform image each time a new VM in the scale set is deployed. See: https://msftstack.wordpress.com/2016/04/20/deploying-applications-in-azure-vm-scale-sets/ for some thoughts on this. Ultimately it might depend on how much you need to install over a base image, and how fast you want scaling to be.
Do you need autoscale based on resource usage or do you plan to manually increase/decrease the number of VMs in the set? See https://azure.microsoft.com/en-us/documentation/articles/virtual-machine-scale-sets-windows-autoscale/
A good way to get started with scale sets is to deploy an existing template directly from Azure Quick start templates. Look at https://github.com/Azure/azure-quickstart-templates and search for vmss. These templates will give you an idea of some of the options you have.
To learn the basics about VM Scale Sets, start with the documentation page: https://azure.microsoft.com/documentation/services/virtual-machine-scale-sets/ and the GA announcement: https://azure.microsoft.com/en-us/blog/azure-virtual-machine-scale-sets-ga/
Also look at higher level services like the Azure Web App service if you haven't already, the advantage of a higher level service is that some of the basic web app operations get taken care of for you: https://azure.microsoft.com/en-us/services/app-service/web/