Fresh install of Eucalyptus 4.0. When I run euca-describe-images no results are returned. Euca-describe-services indicates all services are enabled with the exception of SERVICE imaging and SERVICE loadbalancing .
Do you have any images installed? If there is no image installed in your cloud it is supposed to show nothing iirc.
Did you install any images? (See euca-install-image and euca-import-instance.) It is expected for imaging and load-balacing services to not be enabled until they are installed (See euca-install-imaging-worker and euca-install-load-balancer.).
Related
I have downloaded the wso2 open source of master branch from github, but the build is failing. Can anyone guide me in the right direction? How do I get the publisher and store of wso2 api mananager up?
Make sure you install nodejs and java8(or higher) to your computer. you can try with any version after checking out to the particular tag or if you want the latest release pack, go with the master branch. First build the carbon repo(https://github.com/wso2/carbon-apimgt) and after you build the carbon repo then take the version(it's in main pom file()) of that and update carbon version(<carbon.apimgt.version>) of the product-apim(https://github.com/wso2/product-apim/) main pom file(it's already included a carbon version, replace it to your version). Then build the product-apim.
The master branch is the ongoing development branch. Hence could you please refer this link [1] to get start the WSO2 APIM. This will guide you on how to start publisher and developer portals.
[1]. https://apim.docs.wso2.com/en/latest/getting-started/quick-start-guide
What is the maven version you have in your windows machine? When working with windows it is highly suggested to use compatible versions rather than the latest versions.
so i just started working on a project, and my task is to upgrade sonatype nexus 1.9.x running on CentOS6 to 2.11.x. The old version is currently deployed via a war file. The goal is to get the new version deployed while not breaking builds when devs try to build their project.
My plan of attack is to download nexus. Make the current nexus that is deployed via tomcat, run on a different port, make the new nexus run on the current port, then proxy the old nexus.
Im running into a couple problems though. the old nexus uses java 1.6. If update java to 1.8, would this break the current running nexus?
Would I be able to run two version of nexus on the same vm? If so, how would i do that and minimize the change of messing something up?
Thanks everyone. Im just starting out and this is all very new to me.
Since you Nexus install is very old you have to consider your options:
You could upgrade the existing instance. 1.9 is VERY old so you have to upgrade in multiple steps. First to 2.0, then 2.7 and then 2.11. This is necessary due to data storage changes for configuration and removed upgrade steps.
You could just reconfigure a new server from scratch with the same configuration in terms of repositories and other things and simply rsync the repsitories over to the new storage. You really only have to do this for hosted repositories since the proxy repositories will hopefully still be online and you will just download whatever is requested anew.
If your setup is not too complex I would personally go with option 2. It gives you a chance to revisit things and clean up your setup.
For that setup the steps are roughly.
Install Java 8 in parallel to Java 6
Install Nexus 2.11 from the bundle so it runs with Eclipse Jetty. Do NOT try to run on Tomcat.
Configure it to run on port 9081 or some other non-conflicting port with your original setup and do all the other config including creating the repositories as desired as well as security setup.
Now you should be able to have both servers running.
Create a script that rsyncs the repositories (located in sonatype-work/nexus/storage) and run it with the new server offline
Start the new Nexus in parallel and run a number of tests against it.
Once you have confirmed everything is working plan for a specific time for the cutover and do this
Disable any deployment to Nexus (CI servers, tell people, switch hosted repositories to read only)
Run the rsync script one last time
Turn the old Nexus server off
Configure the new server to use the port of the old one
Start the new one up
You are done. Everything should be good now so the last step is to delete the old Nexus and Tomcat setup.
There are various variations for this process of course. Here are some tips for the rsync.
Also feel free to ping us on the mailing list or chat for further help and check out the comprehensive documentation as well.
I have a router AR1220 VRP V200R001C01SPC500. I'm trying to enable the http service to configure this way, but the command doesn't exist. It a problem with the version? from which version are available this feature?
I've recently manage to configure web mgmt on 2 AR1200 with this version:
AR1200 V200R002C01SPC200
you can download it from support - is general available.
I know that some earlier versions support web mgmt but in chinese so i think you should download and upgrade to AR1200 V200R002C01SPC200 in order to be sure.
Best Regards
Has anyone else had trouble with the new release of Cloudera manager? '4.7' With brand clean ubuntu vm nodes it seems to be placing a file in /etc/apt/sources.list.d called cloudera-manager.list with "http://archive.cloudera.com/cm4/ubuntu/precise/amd64/cm/ precise-cm4.7.0-SNAPSHOT contrib pointed" to as the source, however this url does not exist and when ever it tries to install my nodes if fails.
Does anyone know where this url is kept on the manager so I could change it before it sends it to my nodes?
Greg,
The repository URL is constructed based on the version of the CM server that you are running. So if the server is reporting itself as "4.7.0-SNAPSHOT", then that's what the node installer will use. Now, we've not published any release that describes itself as 4.7.0-SNAPSHOT, so I'm left scratching my head as to how you got into this situation. If you still have that installation, I would recommend that you:
1) Check the reported version of the server from the Support menu at the top right.
2) Check the full package version(s) as reported by "dpkg -l | grep cloudera"
so that we can establish where the build came from.
Thanks.
PS: The installer url you reference in your update is the latest installer and not a 4.6 installer. It's the one people should use for sure.
I am doing some testing to determine resource usage of a rails war. I have used Warbler to package the "15-minute Blog" application using Rails 2.3.5 and JRuby 1.4.0. I am deploying into Tomcat 6.0.24 and create multiple deployments by copying the blog.war file as blogN.war.
This worked great for the first 4 deployments but I can't seem to deploy any more than 4 instances of the war; in other words, the catalina.out log hangs with "Deploying web application archive blog5.war".
Any ideas on what the problem might be or how I might better trouble-shoot this?
Increasing PermGenSpace memory to "-XX:PermSize=64m -XX:MaxPermSize=128m" corrected this problem.
Check your log files, may be the case that your java process, in which tomcat executes, runs out of memory, see java parameters ( -Xmx -Xms ) and http://wiki.apache.org/tomcat/FAQ/Memory . Increasing the available memory may allow you to run more instances of the application.