I can't get nova compute to create an instance of my project.
Could anyone help me debug the problem? It does not create a project via the openstack web interface.
Related
Can I launch a fully functional corda network for a static set of participants without configuring Trust root , NetworkMap or identityManager.
Does a dev setup require any other config apart from Nodes/Notaries?
Corda has the Network Bootstrapper tool which can be used to set-up a static test network for development purposes.
The tool is in fact integrated into the Corda Gradle plugin and it allows you to quickly deploy a test network using simple Gradle commands with some config defined in your Gradle build file.
All our samples also follow the approach of using the static test network.
Refer here to know how to run a Cordapp using test deployment: https://docs.corda.net/docs/corda-os/4.4/tutorial-cordapp.html
I have set up Artifactory OSS Version 6.9.1 on an AWS instance behind an ELB and have been successfully deploying builds to it from GitLab CI/CD. I am now trying to set up a local Artifactory OSS Version 6.10.0 on my laptop so that I can develop builds locally before sharing with the team.
My local artifactory connects perfectly to JCentre and I can browse that repository.
My gradle build will happily connect to the AWS hosted artifactory at http://{URL}/artifactory and resolve my dependencies.
When I connect a remote repository with http://"{URL}/artifactory I get a 500 Internal Error message on Test. If I take off the /artifactory it says it has connected successfully but when I try to browse the remote repo it is empty.
I read Connect one Artifactory to another Artifactory and followed the instructions to edit the json configuration and make the remote repository a smart repository here https://www.jfrog.com/confluence/display/RTF/Smart+Remote+Repositories.
It now has the smart repository image but still cannot be browsed.
Gradle still cannot resolve dependencies with the local artifactory using the remote-repo name.
As stated in the Smart Remote Repository documentation, you should configure the remote repository URL with the following structure:
http://ARTIFACTORY_URL/api/package-type/repository-key
So if you have a Gradle repository named "gradle-test", the URL should be:
http://ARTIFACTORY_URL/api/gradle/gradle-test
Hope this helps.
In the end it turned out to be ridiculously simple. When setting up the remote repository the key needs to be in the url as well as the key field.
So for a repo with a repository key 'fractal' the connection URL is counter-intuitively http:///artifactory/fractal
I am new to cloudify. Can someone please help me in the following?
Deploying a sample application on remote server. Right now I am running the command:
cfy local init --blueprint-path blueprint.yaml --inputs '{"webserver_port": "8080", "host_ip":"ec2-hostname"}'
but it will launch the application on local Cloudify server. Even ec2-hostname is the remote server. But still it is deploying on local server.
Can someone please share the steps required to deploy the application on remote server using Cloudify?
I will highly appreciate it.
Thanks,
Sanjiv
If you're talking about the example described here: http://docs.getcloudify.org/3.3.0/intro/getting-started/ then this is an example to be used in local mode only.
For a more advanced example which can be installed on a remote server, look here: https://github.com/cloudify-cosmo/cloudify-hello-world-example
Scenario
Cloudify 2.7 application running a tomcat service instance
Goal
I would like to stop (shut off) and start the VM hosting tomcat using OpenStack APIs, without Cloudify re-installs the tomcat recipe.
What I tried to do
I tried to use the Maintenance Mode, following this guide:
Setting a service instance to maintenance mode will disable host machine failure detection for that specific service instance.
This means that during the specified time period, a failure or a restart of a service instance host machine will NOT result in a provisioning of a new machine and service instance.
So, I have executed the following commands:
1. cloudify#default> connect VM_MNG_IP
2. cloudify#default> use-application <application_name>
3. cloudify#tommy> invoke <service_name> cloudify:start-maintenance-mode 300
4. Shut off the tomcat VM using OpenStack API
5. Start the tomcat VM using OpenStack API
After that, what I saw in the Cloudify's Orchestraotor logs was the re-installation process of the tomcat service. In other words, the tomcat VM now hosts tow tomcat Processing Units.
ls -al /root/gigaspaces/work/processing-units
<application_name>_tomcat_1_1278947587
<application_name>_tomcat_1_2029943570
Can someone suggest to me what should I do in order to reach my goal?
That is the correct behavior of the default tomcat service provided with Cloudify 2.7 - after a restart, the tomcat files are re-downloaded and deployed locally.
If you want a different behavior, you may want to tweak the tomcat recipe to save the tomcat files in a different location (the default installation saves all files in a per instance work directory, which will be replaced after a reboot). You can change the recipe to look for an existing installation and use it if it exists.
Have a look at the following files:
https://github.com/CloudifySource/cloudify-recipes/blob/master/services/tomcat/tomcat_init.groovy
https://github.com/CloudifySource/cloudify-recipes/blob/master/services/tomcat/tomcat_install.groovy
These are probably the files you will need to edit to achieve what you are looking for. Note how catalina_base is set as a context property, and that AntBuilder is used to download the tomcat installation and save it to a shared location. These are the files you will need to change.
Please consider that Cloudify 2.x has reached end of life - you should consider moving to Cloudify 3: http://getcloudify.org/guide/3.1/quickstart.html
I made a web service. I have made 2 or 3 services and have deployed these on the glass fish. On each service i used package name like pk.mazars.basitMahmood.calculate, pk.mazars.basitMahmood.weather and so on. Means pk.mazars.basitMahmood is common in all packages name. Now i developed a web service on eclipse and now when i try to deploy it, i am getting the following error
cannot Deploy ResourceAEAR
org.eclipse.core.runtime.CoreException: Deployment Error for module: ResourceAEAR:
Error occurred during deployment: Exception while loading the app :
java.lang.Exception: WEB0113: Virtual server [server] already has a web module
[AndroidBackendAuthentication.war] loaded at [/AndroidBackendAuthentication];
therefore web module [ResourceAEAR#AndroidBackendAuthentication.war] cannot be
loaded at this context path on this virtual server. . Please see server.log for
more details.
at com.sun.enterprise.jst.server.sunappsrv.SunAppServerBehaviour.
publishDeployedDirectory(SunAppServerBehaviour.java:859)
...
What is that error mean. How can i resolve it? I also did some google on this error but unable to find exactly where is the problem. So please help :(
Thanks