Trento Node Team added a comment - 11/Nov/14 1:57 PM The public images work correctly. Are you referring at the blueprint images?

Pablo Fernandez Moniz added a comment - 11/Nov/14 5:36 PM We cannot launch images from images section. How to replicate in Trento as example: Switch to Trento region. Click images section. Launch an image (for example ubuntu_12.04.04_new) (Clicking in the Launch button) Set up the info for the instance Launch the instance Go to instances section and wait. Get the error state. You can download a video where we replicate the issue in this link https://mega.co.nz/#!HNt3BYLB!nCB4D-XU06FBkBbi5-razuPjs3JacGECGLkjkFI2lo8 KR

Berlin Node Helpdesk added a comment - 11/Nov/14 7:26 PM You selected two networks: int_net and ext_net. That can fail for various reasons (see OpenStack networking guides). Please try first to launch using only the internal net, then the external net. You may also check which of the two connects to your public router in case you will need a public IP for your experiments. The structure usually is as follows - the VM connects to a private (tenant) net and the private net connects to a default router which in turn connects to a public network from that you can associate a public IP.

Trento Node Team added a comment - 11/Nov/14 11:44 PM as said from Berlin, I just did a test using only int-net and the result is : ACTIVE. Please try and give us a feedback. Thanks

Pablo Fernandez Moniz added a comment - 12/Nov/14 1:02 PM We try to launch new instances as you said, but we still have some issues. Berlin and Waterford don't allow to select any network and fail to create the new instance. Lannion only has a Public-External-Network and it fails too. Trento only works with internal net. We attach some captures of the networking step. Thanks for the detailed response.

Berlin Node Helpdesk added a comment - 12/Nov/14 2:17 PM Berlin does not have predefined networks for a tenant. You need to create one in your tenant first. You also need to create a router for that tenant network if you want to connect to a predefined external network. You cannot directly connect a VM to an external network since those do not provide DHCP. The creation of your VM will fail if it does not get an IP address via DHCP.

Lannion Node Helpdesk added a comment - 12/Nov/14 2:17 PM Pablo, You need to create your own private network before to create an instance. Then assign to your instance a floating IP. BR Riwal

Trento Node Team added a comment - 12/Nov/14 2:51 PM For Trento is ok. After the creation fo the vm you can associate a floating Ip.

Waterford Node Helpdesk added a comment - 13/Nov/14 7:58 AM Hi Sorry for the delayed reply. As stated in ticket "WAT-6" the you will need to build a internal network before you build your local VM instance. If you do not your VM will enter an error state (note1) . A while back this caused us problems as we could not delete these VM from the command line. I have tested this morning and VM creation works (note2) My observations : 1/ The reason why WIT's is different than Lannion node is the fact we do not "share" the external network. 2/ We noticed a while back the spanish node assigns a public IP to "every" VM, and did not have the assign network tab on the "launch" VM wizard. ( an Essex feature? ) 3/ We also noticed that if you create a VM as an admin user it does not matter if the external network is shared. ( AS in if you are an admin user the external network appears in the cloud portal launch wizard ) Regards, Joe. note 1 xifiuser@node-21:~$ nova --os-region-name Waterford list --all-tenants | grep -i error | wc -l 13 note 2 xifiuser@node-21:~$ nova --os-region-name Waterford show b4ed18ab-f304-4dcb-baa2-99b96baa2bed ---------------------------- -----------------------------------------------------------+ Property Value ---------------------------- -----------------------------------------------------------+ status ACTIVE updated 2014-11-13T06:43:18Z OS-EXT-STS:task_state None key_name JtynanXIFIkey image Ubuntu 14.04 server (47645657-138d-4076-9e9b-e5db67d6262c) hostId 829d59a60d6a8082325fb3698a574320ab38819b324959c907fa5dae OS-EXT-STS:vm_state active WIT-net1 network 10.3.4.15 flavor m1.small (2) id b4ed18ab-f304-4dcb-baa2-99b96baa2bed security_groups [{u'name': u'allow-ssh'}] user_id joe-tynan name heldesktest created 2014-11-13T06:43:11Z tenant_id 00000000000000000000000000002900 OS-DCF:diskConfig MANUAL metadata {u'region': u'Waterford'} accessIPv4   accessIPv6   progress 0 OS-EXT-STS:power_state 1 OS-EXT-AZ:availability_zone nova config_drive   ---------------------------- -----------------------------------------------------------+