Hi KT,
A few issues to deal with there...
We're not responsible for all of these points, but we'll try to help as much as a we can.
First, we're still looking into the volume issue - the problem still manifests for us. We're waiting on feedback on that point while also pursuing further testing.
So, to address your issues:
> => Instance ubuntu14_2016
> <https://cloud.lab.fiware.org/#nova/instances/a4a80f4c-a6a2-4a26- 960b-5843afad2c09/detail>
> =>I test this problem by launching a brand new ubuntu image into
instance ubuntu_14.04
> <https://cloud.lab.fiware.org/#nova/instances/5347e11f-4af3-4716-b0a2-fe1aa50c0543/detail>
> ( test). I am able to ssh login in and run
> sudo apt-get update (without problem)
Ok - that is good - this is the image provided by Fiware and it
seems to work sensibly.
> => Clearly, something strange happens to theubuntu14_2016
> <https://cloud.lab.fiware.org/#nova/instances/a4a80f4c-a6a2-4a26-960b-5843afad2c09/detail> , which I have been working without problem (e.g.
> sudo apt-get update)
> Please grant me root access again so I can continue with my development work.
> Thanks again for excellent timely support!!!!!
So I've checked out the VM and the image.
The VM is based on the image
ubuntu14-jan2016 (34939e0c-2920-4861-a99b-afb3dd0edbf1)
This is not one of the official Fiware images. Details on this image
are as follows:
root@node-1:~# glance image-show 34939e0c-2920-4861-a99b-afb3dd0edbf1
------------------------------------------------------+
------------------------------------------------------+
checksum |
8bb7b4293a3d8b64509d7515ff4b34ef |
container_format |
bare |
created_at |
2016-01-18T09:52:46 |
deleted |
False |
disk_format |
raw |
id |
34939e0c-2920-4861-a99b-afb3dd0edbf1 |
is_public |
False |
min_disk |
40 |
min_ram |
0 |
name |
ubuntu14-jan2016 |
owner |
00000000000000000000000000006770 |
protected |
False |
size |
42949672960 |
status |
active |
updated_at |
2016-01-18T14:43:04 |
------------------------------------------------------+
You can see that this is a private image to the account 6770
(your account). You can also see that it is not a public image
('is_private' set to False).
So, I don't know what this image is or where it came from. This
makes it difficult to address issues relating to it as I'm sure you
understand. Do you have any info on where this image came from
which could help us understand what we are dealing with?
Next issue:
> Dear Seán
> What is the best practice to add new port to the "Security Groups"
> I have added new ports, I have tried different ways to make these ports work. Including creating a new instance using the security Groups with new ports, no luck.
> Any suggestion? How to the newly added ports get reflected in the running instance?
To be clear here, I assume you're asking about opening ports.
To add a new port to an existing secgroup, you need to select the
secgroup by clicking on the security panel on the left and then the
security groups tab on the top. Then you select the secgroup you
want to modify. Check the box, then go to actions. Edit rules. Add a rule indicating the source port and the destination port (usually the port you want to open on your VM) and make the CIDR 0.0.0.0/0 to enable access to this port from anywhere on the internet. Then click on Add rule and the rule should appear in your secgroup.
The rules for the secgroups get applied instantly, I think.
> Dear Seán,
> It seems that the password I used to enable sudo (root) no longer valid.
> Very strange.
> Please reset these password or mail the temporary password DIRECTLY to my email. Thank you.
Right now, we cannot reset the root password of your VMs, I'm afraid.
Is this a big problem? Can you just restart a new VM - is there much info on this VM which you need to keep?
BR,
Seán.
Closing ticket due inactivity.
BR,
Bruno.