The issue has been emailed:

• Time sent: 30/Oct/15 2:48 PM
• To: bernie@anysolution.eu
• with subject: *(HELC-1119) Problems setting up an Instances in Fiware Lab. *
  

Dear Bernie,

I've moved your request to the coaches help desk so that you coach can help you. Additionally, I'm requesting help to the Spanish node for you.
If needed, we could also address the GE Owner - Orion.
But I think the coach and the spanish lab should be able to help you to overcome the situation.

Have a nice weekend
Kind regards,
Manuel

Sorry about that here is the plain text version.
Best Regards
Bernie

Dear Fiware-Help Team,

I have been trying for days now to make instances of GEs in our Fiware
Lab account with no success. We are working in Authorized regions:
Spain2.
I have tried to make the Instances by the Blueprint Template method and
by using the Instance image method. What ever I do I cannot produce an
operational Instance. I have tried with Orion, the Orion Bundle, the GUI
maker and the IoT Broker. I have numerous error message such 'name not
correct, and 'no more floating IPs available and others. I am
continually asked to do things using SSH but as I have no IP address to
work with I cannot enter the SSH system using the terminal.
The major problem is, this work is required for a Soul-Fi B funded
project. The midterm report is required on December 7 and the project is
to be finished by 22 February 2016. The more time we spend trying to get
the Fiware Lab side working the less time we have to develop the special
IoT systems and hardware that are essential for the project's success. I
have tried to solve this problem by using the communications in
Fiware-Help but there is such an array of problems highlighted there
that even if I find something related it inevitably does not solve my
problem. I have now cleared all my previous work from Fiware-Lab and
below I have included my final attempt to make an instance of Orion and
the feed back I am getting from the system. We need some serious support
on this issue or our project will be in serious jeopardy. In the
meantime I will continue with the development of our IoT hardware and
software system using solutions with Google Docs, Dropbox apps, Temboo
etc and then attempt to migrate these to Fiware-Lab if we can solve the
problems.
Unfortunately I am now receiving notifications from
no-reply@account.lab.fiware.org that Spanish node (Spain2) is under
maintenance for the next few days with accompanying outages which may
further delay our progress.

Record of attempt to make an Instance of Orion using the image method.

Step 1. Go to Instances > Images.

Step 2. From the Image list select 'orion-psb-image-R4.2

Step 3. The system presents the following information.
Info
Name: orion-psb-image-R4.1
ID: 83a74688-f0df-4369-a22f-2b75e73f20e6
GE ID: 344
Status
Status: active
Public: True
Checksum: d3b493a80b2d0ba74fd7b7e73b0ddcf4
Created: 2015-03-09T08:15:45.000000
Updated: 2015-09-24T13:15:53.000000
Specs
Size: 4.7 GB
Container Format: ovf
Disk Format: qcow2

Step 4. Launch Image' Button.

Step 5. Fill in the Launch Instance form as follows
Instance Name: slorion
Flavour: m1.small
Instance count: 1

Step 6. Click the 'Next' button
Step 7. Fill in the Launch Instance form as follows
Keypair: smartlock_orion
Security Group: smartlock_orion

Step 8. Click the 'Next' button

Step 9. Fill in the Launch Instance form as follows
Selected Networks: node-int-noinet-net-02

Step 10. Click the 'Next' button

Step 11. The customization Script is presented but no action is taken

Step 12. Click the 'Next' button

Step 13. The system now presents the following information.
Instance Name: slorion
Image: orion-psb-image-R4.1
Flavor: m1.small
Instance Count: 1
Keypair: smartlock_orion
Security Group: smartlock_orion
To access the instance:
You need to include a security group with port 22 opened to access via
SSH.
You need to assign a floating IP to access from a external network.

Step 14. Click the 'Launch instance' button

Step 15. The system now redirects to
https://cloud.lab.fiware.org/#nova/instances/ which is a Blank Black
screen.
Clicking on this screen redirects to
https://cloud.lab.fiware.org/#nova/instances/ which presents the
following information:
Instance Name. slorion
IP Address. 192.168.128.206
Size. 2048 MB RAM | 1 VCPU | 20GB Disk
Keypair. smartlock_orion
Status ACTIVE
Task. None
Power State- RUNNING

*But this instance is repeated in the list three time*.
The communication panel atr the bottom of the page reports:
Success: Instance slorion launched.

All of this is new I have never at this point I normally get messages in
the panel such as:
Error: undefined. Cause: 400 Error info OR
Error: Error releasing floating IP 10.1.64.121. Cause: 503 Error OR
Error: Error launching instance slorion. Cause: 403 Error info

Step 16. Click on the first instance of slorion in the list and the
following information is displayed.
Overview
Info
Name: slorion
ID: 94a025d8-a247-4ebe-9e6d-c6227fdca35f
Status: ACTIVE

Specs .
RAM: 2048MB
VCPUs: 1VCPU
Disk: 20GB

IP Addresses : node-int-noinet-net-02: 192.168.128.206

Security Groups: smartlock_orion

Meta
Key name: smartlock_orion
Image Name: orion-psb-image-R4.1
region: Spain2

Volumes :

Installed Software : Image orion-psb-image-R4.1 does not allow Software
Management with SDC.

Step 17. Click on Connection tab and the following information is
presented.
Connect using a SSH client
You need to associate a Floating IP to this Instance in order to connect
via SSH.
Go to Security -> Floatings IPs
If you have not any Floating IP available, allocate a new one to the
project.
Associate a Floating IP to this Instance.

Connect to VM display

Connect directly to the Virtual Machine display [View Display Button]

Step 18. Go to Security -> Floatings Ips The following information
appears.
IP Address: 10.1.64.121
Instance: -
Fixed Address:
Floating IP Pool: fedoration-ext-net-01

Step 19. Click on Actions drop down list. Click on Associate IP. In
the form that appears associate the IP with the Instance slorion. The
following information appears
IP Address: 10.1.64.121
Instance: slorion
Fixed Address: 192.169.128.206
Floating IP Pool: fedoration-ext-net-01

NOTE: At this point I had to log into Fiware Lab again ??
When I went back to Instances > Connection I was presented with this
information:

Connect using a SSH client
Ubuntu/Mac terminal
1. Open the Terminal
2. Locate the keypair asocciate to this Instance when launching it.
my_keypair.pem
3. Modify the keypair permissions in order to make it not publicly
viewable.
chmod 400 my_keypair.pem
4. Connect to the Instance using its public IP.
ssh -i my_keypair.pem root@10.1.64.121

Windows PuTTY Client
1. Install PuTTY and PuTTYgen from Putty website.
2. Locate the keypair asocciate to this Instance when launching it.
my_keypair.pem
3. Convert your Keypair (.pem) to PPK with PuTTYgen.
4. Use PuTTY to connect to the Instance using its public IP
(10.1.64.121) and the new PPK Keypair.

Connect to VM display

Connect directly to the Virtual Machine display
[View Display] Button

Step 20. Click on the [View Display] button. The display appears and
after clicking on the [Send
CtrAltDel] Button the following text appears in the display.
“
Cent0S release 6.3 (Final)
Kernel 2.6.32-279.14.1.e16.x86_64 on an x86_64
Host-192-168-128 log in: _”
“

If I enter my Fiware Lab password here I get the response 'Password
Incorect'

If I try to enter SSH with:
ssh -i smartlock_orion.pem root@10.1.64.121 (Note. smartlock_orion is
the keyword pair)
I get the response:
Warning: Identity file smartlock_orion.pem not accessible: No such file
or directory.

If I enter into my browser either of the IP Addresses 10.1.64.121 OR
192.168.128.206 I continually receive the error message 'The connection
was reset'

Conclusion:

This is the most progress that I have made in days. This may be as a
result of the maintenance work that has been carried out on the Spanish
node (Spain2), but I still do not seem to be getting anywhere.
I am lost, I do not know where to go from here.

With Kind Regards
Bernie

Dear Bernie,

For some reason I cannot open the file, would you please explain it in plain text.

Thanks in advance!
Manuel