I am creating wso2 Paas on Amazon Ec2 by following the instructions in Quick Start Guide with Screencasts. After running the ./boot.sh am getting the following message.
Starting WSO2 Private PaaS server as ubuntu user...
Nothing happens after this message and the terminal is frozen after 2 hours.
I am using centos 6.7, screen terminal and amazon ec2 instance type is t1.micro, ami is Private PaaS ami-4e062c1c for doing this.
Please suggest a solution for this.
WSO2 has discontinued WSO2 Private PaaS solution. Please refer [1] for the new PaaS strategy. On AWS, WSO2 middleware can be deployed either on VMs using AWS deployment automation and autoscaling features or with containers using Kubernetes, DC/OS, ECS.
[1] http://wso2.com/cloud/paas/
Related
We are deploying multiple service in ECS cluster with fargate, On the front end we are using nginx service. On the backend some services are getting deployed frequently. Once any of the backend service deployed we manually need to update nginx service forcefully. Do we have any approach to update only nginx service forcefully when any of the new service deployed successfully?
How we can achieve this ? using lambda or cloudwatch....
Any help is appreciated, Thanks in advance
When the backend Services are updated you can use cloud watch to trigger a lambda. This lambda can use the AWS SDK to to restart the Nginx container service/task. You could also version your Nginx container along with all your backend services so that that the a new Nginx image is push up when your backend changes and the task definition is changed contains the new image. Providing your using AWS ECS Service it can update it self.
See here for more information: https://docs.aws.amazon.com/AmazonECS/latest/developerguide/update-service.html
Is there a way to host Moqui on AWS? I was trying to host Moqui using a EC2 instance but couldn't figure out a way to connect them.
The Run and Deploy document on moqui.org has a section for a simple recommended deployment using ElasticBeanstalk and RDS:
https://www.moqui.org/m/docs/framework/Run+and+Deploy#AWSElasticBeanstalkandRDS
With more details about how you want to set things up on AWS the answer to how might vary from this.
For clustered setups things get more involved to get the right settings for Hazelcast AWS discovery and it is best to use an external ElasticSearch server like an AWS ElasticSearch instance and configure Moqui using environment variables to use the Java REST Client mode instead of the Embedded Node mode. Settings for the moqui-hazelcast and moqui-elasticsearch components can be seen in the MoquiConf.xml file in each component.
Hey I'm running a Kubernetes cluster on Azure using ACS.
My question is if there is any way to add a Windows agent to the cluster without completely rebuilding the cluster?
I know this is possible for Linux distro's depending on what you use but I wonder if anyone knows a way to do this for Windows agents?
If you have deployed your cluster using the Azure portal then you can simply follow the instructions here https://learn.microsoft.com/en-us/azure/container-service/container-service-scale
But if you have deployed using the ACS engine and ARM template then currently there is an issue that it does not creates the acs resource.
I have an image in a private Docker Hub repository, which I'm trying to deploy on Amazon's Elastic Container Service. There seems to be nice web console to run a container from a public repository, but nothing for private. I've read and tried to understand the documentation for this, but I don't understand what that has to do with deploying my container, as it states "The Amazon ECS container agent allows container instances to connect to your cluster".
As an alternative to using the web console, I see mentions of setting up a task definition. It sounds like that's the manual version of what the web console does. I suspect my best bet is with this method, possibly with the help of the script here.
What is the simplest way for me to run an existing image on ECS that's hosted in a private repository?
Right, so a container instance is just the EC2 machine that happens to run the services defined in the cluster. The cluster can then connect to the EC2 machine as a container instance, but unless the EC2 machine is appropriately configured, it can't run your private repository.
I'm trying to setup a database with Deis. I know this is possible, but there doesn't seem to be any documentation about how to do it other than setting an ENV variable.How could I setup say a MongoDB or Cassandra docker container and then deploy that and have my deis app use it?
If you're trying to deploy now, a possible solution is to set up a docker container, have it publicly route-able, and then configure your application to use that container through an environment variable following Heroku's 12 factor app best practices. There is a feature request for a Deis service gateway that will act like Heroku's Add-on Marketplace, but it's not there yet.