Instance VM Creation - fiware-orion

I was trying to launch a instance VM to do some test. I selected the image orion-psb-image-R4, but when I launch the instance, an error appears:
(Status:ERROR Power State:No State), is impossible to associate an a Public IP (Error: undefined. Cause: 400 Error info).
I created my key pair, my public IP and my security group (I'm using the default security group, but I created two new rules to use ports 1026 and 22), entered image description, then trying to launch a instance VM to do some tests.

Taking into accoun the comments to this question, this is an specific question related with the FIWARE Lab cloud infrastructure, rather than with Orion Context Broker itself, and there are better channels to deal with it. Please send an email to fiware-lab-help#lists.fi-ware.org in order that we can make a following or this issue and you can know when it was resolved.
Please take into account that the more details (region, id of the instance, image, etc.) you give us as the more help us to resolve the problem

Related

Import a custom Linux image for POWER-IAAS part of the IBM Cloud?

I am trying to import a cloud-enabled Debian Linux image for the Power architecture to run on the IBM public cloud, which supports this architecture.
I think I am following the instructions, but the behavior I am seeing is that, at image-import-time, after filling in all the relevant information, when I hit the "import" button, the GUI just exits silently, with no apparent effect, and no reported error.
I am reasonably experienced doing simple iaas stuff on AWS, but am new to the IBM cloud, and have not deployed a custom image on any cloud provider. I'm aware of "cloud-init", and have a reasonable general knowledge of what problem it solves (mapping cloud-provider metadata to config entries in the resulting VM at start-time), but not a great deal about how it actually works.
What I have done is:
Got an IBM cloud account, and upgraded out of the free tier, for access to Power.
Activated the Power Systems Virtual Server service.
Activated the Cloud Object Storage service.
Created a bucket in the COS.
Created an HMAC-enabled service credential for this bucket.
Uploaded my image, in .tar.gz format, to the bucket (via the CLI, it's too big to upload by GUI).
The image is from here -- that page is a bit vague on which cloud providers it may be expected to work with, but AFAIK the IBM cloud is the only public cloud supporting Power?
Then, from the Power Systems Virtual Server service page, I clicked the "Boot Images" item on the left, to show the empty list, then "Import Image" at the top of the list, and filled in the form. I have answers for all of the entries -- I can make up a new name, I know the region of my COS, the image file name" (the "key", in key-object storage parlance), the bucket name, and the access key and secret keys, which are available from the credential description in the COS panel.
Then the "import" button lights up, and I click it, and the import dialog disappears, no error is reported, and no image is imported.
There are various things that might be wrong that I'm not sure how to investigate.
It's possible the credential is not connected to the bucket in the right way, I didn't really understand the documentation about that, but in the GUI it looks like it's in the right scope and has the right data in it.
It's also possible that only certain types of images are allowed, and my image is failing some kind of validation check, but in that case I would expect an error message?
I have found the image-importing instructions for the non-Power-IAAS, but it seems like it's out of scope. I have also found some docs on how to prepare a custom image, but they also seem to be non-Power-IAAS.
What's the right way to do this?
Edit to add: Also tried doing this via the CLI ("ibmcloud pi image-import"), where it gets a time-out, apparently on the endpoint that's supposed to receive the image. Also, the command-line tool has an --os-type flag that apparently only takes [aix | sles | redhat | ibmi] -- my first attempt used raw, which is an error.
This is perhaps additional evidence that what I want to do is actually impossible?
PowerVS supports only .ova images. Those are not the same supported by VMWare, for instance.
You can get from here https://public.dhe.ibm.com/software/server/powervs/images/
Or you can use the images available in the regional pool of images:
ibmcloud pi image-list-catalog
Once you have your first VM up and running you can use https://github.com/ppc64le-cloud/pvsadm to create a new .ova. Today the tool only supports RHEL, CentOS and CoreOS.
If you want to easily play with PowerVS you can also use https://github.com/rpsene/powervs-actions.

AWS EC2 Instance causing ERR_CONNECTION_RESET on some networks, but works fine on others

I am using an EC2 instance as a backend database server that receives open listings for an AirBnB type site. I've checked on my own browsers and phones and had others check on theres in other regions as well, and these listings load perfectly fine for us. There is one person in another region, however, who is not seeing any listings at all and receives the Failed to load resource: net::ERR_CONNECTION_RESET error instead. I even had them try clearing their cache in Chrome, but that did not help. Below are photos depicting the situation:
Click here to see the problem page (lol)
Photos depicting errors:
What I See/What Should Show Up:
Black Listings Come Up For Them
Here Are The Errors They Receive
Here are the Inbound settings for my security group
I'm thinking it may be a firewall issue, but i'm just not sure. Any help would be greatly appreciated, thank you!
i would suggest you check the security group in which your machine is, since it's possible that you're not allowing traffic to reach your machines.
it's possible that your location IP is open to the API but not other IP's.
I've tried to reach your page from my place and it's timing out as well, that points to the security group.
if possible share a screenshot of the security group set up on your machine, that will help diagnose further.

Network error while setting up context mapping - IBM Bluemix

I am getting network error every time and on every available device when I am trying to setting up Context Mapping, I am not sure if it is really due to Network as I am able browser any where else.
See the image for more details
The solution to this error is to confirm that you are in proper region.
You can change the region from Account > Region. Set your region. Please see the image.

Multiple consoles for one user

I recently signed up for bluemix and suddenly I see two consoles url when I try to log in. Which is confusing me.
Can some one explain the difference between these.
https://console.eu-gb.bluemix.net/
and
https://console.ng.bluemix.net/
I can see all my test application that I created are part of "https://console.ng.bluemix.net/"
Though bluemix is allowing me to create applications in "eu-gb" doamin as well.
Bluemix has different hosting regions and you can create apps and services in them. Right now there are two hosting regions (data centers) for the public Bluemix. Hence the two consoles you are seeing.
Try switching to the "eu-gb" region, create a service there, and notice that the second console shows a service, too. :)

Using PEP-Proxy to secure my data on Orion Context broker at virtual image

I have created an image of Orion Context Broker and created some entities and their attributes, but on accessing in address bar everyone can access that data and modify it. I need to secure that data by pep-proxy.
IP: http://a.b.c.d:8080/v1/contextEntities/
or do I need to use only the global instance for creating new entities.
Please tell me in which files I have to change in order to get it secure.
I have pre-installed orion-pep-proxy on my virtual image (system).
Thanks in advance
Please have a look to the authorization section in the Orion User Manual. There you will find references to the documentation on the different PEP alternatives you have to protect your Orion instance (Wilma and Steelskin implementations at the time being).