Open Stack

Clint,

yeah sorry, I meant boot to the network named "demo-net". I think you may have the credentials of the admin user in your environment, but demo-net belongs to user "demo". I think you need to open a new console and load the credentials of the demo user into its environment, then try the boot command again.


keystone tenant-list

quantum net-list -c id -c name -c tenant_id


To see which credentials you have in you environment do:

set | grep ^OS

Re, Darragh.


>________________________________
> From: Clint Dilks <clintd at waikato.ac.nz>
>Cc: "openstack at lists.openstack.org" <openstack at lists.openstack.org> 
>Sent: Wednesday, 25 September 2013, 0:06
>Subject: Re: [Openstack] OpenStack Grizzly Quantum Networking
> 
>
>
>Ok
>
>So looking at this further I believe I am doing something wrong with the virtual networking rather than the physical side of things.
>I now believe that what Darragh means is that my instances should boot on the internal virtual network rather than the public, which makes sense but there is a issue that I don't understand.  
>
>
>net-list shows two networks at I would expect, so I believe that I should be able to tell a vm to boot using demo-net but the tools only allow me to boot if I specify the network as public.  What could be wrong here ?
>
>
>
>
>[root at blitzen ~]# quantum net-list
>+--------------------------------------+----------+------------------------------------------------------+
>| id                                   | name     | subnets                                              |
>+--------------------------------------+----------+------------------------------------------------------+
>| b04a786f-d251-4796-bfcf-6486bec467db | demo-net | 06075526-7210-461b-94f1-87c25ad231ab 10.10.11.0/24   |
>| f2c7206c-a860-4206-ab5b-34bd9b7d2553 | public   | f326c5d0-f127-4da5-9065-c3211c9a81b8 130.217.79.0/24 |
>+--------------------------------------+----------+------------------------------------------------------+
>
>nova boot --flavor 1 --image f5058a7e-b0dc-4be2-983e-822f7e586090 --key-name default_key  --nic net-id=b04a786f-d251-4796-bfcf-6486bec467db clintd
>ERROR: The resource could not be found. (HTTP 404) (Request-ID: req-0d538673-43ff-4a11-9aba-3b907c129e5c)
>
>nova boot --flavor 1 --image f5058a7e-b0dc-4be2-983e-822f7e586090 --key-name default_key  --nic net-id=f2c7206c-a860-4206-ab5b-34bd9b7d2553 clintd
>+-------------------------------------+--------------------------------------+
>| Property                            | Value                                |
>+-------------------------------------+--------------------------------------+
>| status                              | BUILD                                |
>| updated                             | 2013-09-24T22:47:27Z                 |
>| OS-EXT-STS:task_state               | scheduling                           |
>| OS-EXT-SRV-ATTR:host                | None                                 |
>| key_name                            | default_key                          |
>| image                               | Fedora                               |
>| hostId                              |                                      |
>| OS-EXT-STS:vm_state                 | building                             |
>| OS-EXT-SRV-ATTR:instance_name       | instance-0000000d                    |
>| OS-EXT-SRV-ATTR:hypervisor_hostname | None                                 |
>| flavor                              | m1.tiny                              |
>| id                                  | b09b9547-be68-49e0-b271-f57515e44a54 |
>| security_groups                     | [{u'name': u'default'}]              |
>| user_id                             | 19839209541e446da8642c67e82a63ab     |
>| name                                | clintd                               |
>| adminPass                           | chRqXA9mQhxp                         |
>| tenant_id                           | b41aca749a214b449ad6b3a124d113f7     |
>| created                             | 2013-09-24T22:47:27Z                 |
>| OS-DCF:diskConfig                   | MANUAL                               |
>| metadata                            | {}                                   |
>| accessIPv4                          |                                      |
>| accessIPv6                          |                                      |
>| progress                            | 0                                    |
>| OS-EXT-STS:power_state              | 0                                    |
>| OS-EXT-AZ:availability_zone         | nova                                 |
>| config_drive                        |                                      |
>+-------------------------------------+--------------------------------------+
>
>
>
>
>
>
>
>
>
>On Wed, Sep 25, 2013 at 9:08 AM, Clint Dilks <clintd at waikato.ac.nz> wrote:
>
>Hi 
>>
>>Thanks to everyone whom replied to this thread I will try deleting the ports shortly.
>>
>>
>>
>>
>>
>>
>>
>>Clint,
>>>
>>>you need to boot your VMs attached to the private network and not the public network. Then you must allocate and associate floating ips. Also remember to open ports in the security groups.
>>>
>>
>>
>>
>>Darragh,
>>
>>
>>In the guide I was following they used two networks 
>>
>>
>>10.10.10.0/24 (which they call internal)
>>
>>10.0.0.0/24 (which they call external)
>>
>>
>>So I believed I should be able to replace where ever they use 10.0.0.0/24 with 130.217.79.0  (br-ex is currently attached to an address in this range)
>>
>>
>>Are you saying that in fact I should have two private networks say mirroring the guide, but then also have a nic configured for 130.217.79.x ?
>>
>>
>>Or do you just mean that keeping things as I have them currently I should just create the public-subnet within the 10.10.10.0/24 ?
>> 
>>
>>
>>
>>
>> 
>>
>>>Re, Darragh.
>>>
>>>
>>>
>>
>
>
>