I am trying to use the nova boot command but i keep getting the "to few arguments" error.
nova boot --image this --flavor is --key-name usless --availability-zone nova:ubuntu
I have been at this for a while can someone just please post what i am doing wrong and not post a link. I have followed a few and have been going in circuls this whole time. That and what is --key-name.
It is correct the nova boot command that you put. Where is the name of the server?
Related
I got a Ocelot Gateway projet and I try too add an new API in the docker-compose, but I got an error tell me :"docker support the solution file must be located in the same or higher folder".
So after multiple try, I decide to add the dockerFile manually (I want to add the "TokenServerOcelot").
But I got the error:
Error DT1001
here is my code:
Dockerfile
docker-compose.yml
docker-composer.override.yml
If someone got any idea this would help me a lot ! :)
Thanks
I try too add by the Container Orchestrator Support but it didn't work, so i try by adding to TokenServerOcelot the docker file and I got the DT1001 error
I'm getting this error trying to deploy a card to a working blockchain on cloud, any idea? Thanks in advance. I'm using a mac, following the guide (Kubernetes installed/configured well, I think):
https://ibm-blockchain.github.io/interacting/
./create/create_composer-rest-server.sh --paid --business-network-card /Users/sm/jsblock/tutorial-network/PeerAdmin#fabric-network.card
Configured to setup a paid storage on ibm-cs
Preparing yaml file for create composer-rest-server
sed: 1: "s/%COMPOSER_CARD%//User ...": bad flag in substitute command: 'U'
Creating composer-rest-server pod
Running: kubectl create -f /Users/sm/jsblock/ibm-container-service/cs-offerings/scripts/../kube-configs/composer-rest-server.yaml
error: no objects passed to create
Composer rest server created successfully
There is an error in that document. And you are also specifying the Peer Admin card when you need to use a Network Admin Card.
There are 2 sets of 'parallel' documents for paid and free clusters. The command you are using has --paid in it in error. If you remove --paid and use the Network Admin Card I think it will solve the problem.
Your command will look something like this: ./create/create_composer-rest-server.sh --business-network-card admin#YOUR-network
I tried again with the install proccess (deployed blockchain instance seemed to work weall): https://ibm-blockchain.github.io/simple/
But I noticed that the script:
./create_all.sh
...never ended (mostly an internal kubernetes problems I guess). And I reset the installation:
./delete_all.sh
./create_all.sh
I tried again, now everything Ok. I could get my awesome API REST talking with my Hyperledger Blockchain, deployed on IBM Cloud. Ready to develop something amazing.
I was testing OpenWhisk on Bluemix. What i want to do is very very simple. I have a js script that works (it's just a console.log). I have a Dockerfile making a docker .. when i run my docker i can see my console.log \o/ (i know it's amazing)
Then i create my action ......
I try to run it from Bluemix UI
I get this :
failed to invoke action XXX/XXXX: Container hash or name expected in makeContainer.
Just what does it means ? I couldn't find anything on it.
ps : If you know where i can find some real doc about how to use docker container for actions i would be very happy :).
Thanks a lot for your help.
Edit : In the end the problem was that i was trying to pull from a private docker repo. I have to say the error message is not explicit x). Thanks for your help.
You can find the documentation about creating docker actions here: https://new-console.ng.bluemix.net/docs/openwhisk/openwhisk_actions.html#openwhisk_actions_docker
Instructions helps you download the docker sdk for OpenWhisk, and allow you to create a docker action that you can invoke from CLI or Web UI.
If you create the action using the Web UI you need to specify the docker Image from Docker hub using the format username/imagename like openwhisk/example
If you need more help feel free to reach the team on Slack for more real time interactions and we should be able to help you and get your feedback on how can we improve the user experience.
Team: https://developer.ibm.com/open/slack-request
Channel: #openwhisk https://dwopen.slack.com/messages/openwhisk
This error seems like a Bluemix internal error to me.
I try to add another route using the new Bluemix dashboard to one of my liberty apps and the error message I get is:
BXNUI0030E: The 'xxxxxx.au-syd.mybluemix.net' route wasn't mapped to
the 'xxxxx-arya' app because a problem occurred contacting Cloud
Foundry. Try again later. If you see this message again, go to the
Bluemix status page to check whether a service or component has an
issue. If the problem continues, click the Account and Support icon in
the top menu bar, click Get help, and search for help or get support.
The error message is not clear to identify cause of the problem. The message just tells Cloud Foundry command behind Web interface failed to create map-route, but it didn't tell what exactly happen. Please run below commands to know what happened during creating map-route and fix the problem;
Login into the space by cfcli;
cf login -a api.au-syd.bluemix.net -u -p -o -s
List all routes in the space and make sure the app or the map-route are there;
cf routes
Create map-route by command;
cf map-route APPNAME au-syd.mybluemix.net --hostname NEW-HOSTNAME
Check error message and fix the problem
*) Most common problem is duplicate map-route name if the hostname used in in other spaces. Please contact Bluemix Support with your new hostname if you cannot find the hostname in your organizations.
I tried to access a web application while it was in the process of redeploying or reloading, and I just got a 404 error. This is likely to result in time-wasting helpdesk calls if a user happens to see it. How can I replace the 404 message with something more helpful, like "This application is being upgraded - check back in a minute or two"?
You may want to consider looking at Application Versioning feature to "pre-deploy" an application to minimize the impact.
Deploy your app:
$ asadmin deploy myapp.war
Deploy version2 in "disabled" mode, meaning the old version is still active:
$ asadmin deploy --enabled=false --name myapp:version2 myapp.war (version2 is an arbitrary name)
When ready to activate version2:
$ asadmin enable myapp:version2
The nice thing about this approach is that if you run into issues with version2, you can always fall back to the original version:
$ asadmin enable myapp
I normally deploy my webapps behind an Apache proxy. When the appserver goes down Apache returns a 503 response.
This can be customised with an alternative "I'm sorry we're doing maintanence" message
You can also customize the standard response codes (403, 404, etc.) in the server configuration. The simple change is to change the message text, but it isn't as elegant as what you are looking for. However, there will always be a point where the environment will return 404, 503, etc., so you might consider adding this, in addition to, the "behind the proxy" answer provided by #Mark O'Connor.