Mailing List Archive

Help with meta-data
Hi all,

I've completed the excruciating Launchpad process of subscribing to a
mailing list to ask for your help with having my instances access their
meta-data.

I'm new to OpenStack. So please forgive my n00bness.

I installed OpenStack on Ubuntu 12.04 by following stackgeek's 10 minute
method and using their scripts:
http://stackgeek.com/guides/gettingstarted.html

Which got me quite far. I had to fix some of the networking setup. Now I
can launch instances and ping them.

However, they cannot access their meta-data:

Begin: Running /scripts/init-bottom ... done.
cloud-init start-local running: Wed, 08 Aug 2012 07:33:07 +0000. up 8.32 seconds

no instance data found in start-local

ci-info: lo : 1 127.0.0.1 255.0.0.0 .

ci-info: eth1 : 0 . . fa:16:3e:5a:f3:05

ci-info: eth0 : 1 192.168.1.205 255.255.255.0 fa:16:3e:23:d7:7c

ci-info: route-0: 0.0.0.0 192.168.1.1 0.0.0.0 eth0 UG

ci-info: route-1: 192.168.1.0 0.0.0.0 255.255.255.0 eth0 U

cloud-init start running: Wed, 08 Aug 2012 07:33:10 +0000. up 11.95 seconds

2012-08-08 07:33:54,243 - util.py[WARNING]: 'http://169.254.169.254/2009-04-04/meta-data/instance-id' failed [2/120s]: url error [[Errno 113] No route to host]

2012-08-08 07:33:57,242 - util.py[WARNING]: 'http://169.254.169.254/2009-04-04/meta-data/instance-id' failed [5/120s]: url error [[Errno 113] No route to host]

2012-08-08 07:34:01,246 - util.py[WARNING]: 'http://169.254.169.254/2009-04-04/meta-data/instance-id' failed [10/120s]: url error [[Errno 113] No route to host]

2012-08-08 07:34:04,246 - util.py[WARNING]: 'http://169.254.169.254/2009-04-04/meta-data/instance-id' failed [13/120s]: url error [[Errno 113] No route to host]

2012-08-08 07:34:07,246 - util.py[WARNING]: 'http://169.254.169.254/2009-04-04/meta-data/instance-id' failed [16/120s]: url error [[Errno 113] No route to host]

2012-08-08 07:34:10,246 - util.py[WARNING]: 'http://169.254.169.254/2009-04-04/meta-data/instance-id' failed [19/120s]: url error [[Errno 113] No route to host]

2012-08-08 07:34:13,246 - util.py[WARNING]: 'http://169.254.169.254/2009-04-04/meta-data/instance-id' failed [22/120s]: url error [[Errno 113] No route to host]

2012-08-08 07:34:16,246 - util.py[WARNING]: 'http://169.254.169.254/2009-04-04/meta-data/instance-id' failed [25/120s]: url error [[Errno 113] No route to host]

2012-08-08 07:34:21,250 - util.py[WARNING]: 'http://169.254.169.254/2009-04-04/meta-data/instance-id' failed [30/120s]: url error [[Errno 113] No route to host]

2012-08-08 07:34:24,250 - util.py[WARNING]: 'http://169.254.169.254/2009-04-04/meta-data/instance-id' failed [33/120s]: url error [[Errno 113] No route to host]

2012-08-08 07:34:29,254 - util.py[WARNING]: 'http://169.254.169.254/2009-04-04/meta-data/instance-id' failed [38/120s]: url error [[Errno 113] No route to host]

2012-08-08 07:34:35,258 - util.py[WARNING]: 'http://169.254.169.254/2009-04-04/meta-data/instance-id' failed [44/120s]: url error [[Errno 113] No route to host]

2012-08-08 07:34:41,261 - util.py[WARNING]: 'http://169.254.169.254/2009-04-04/meta-data/instance-id' failed [50/120s]: url error [[Errno 113] No route to host]

2012-08-08 07:34:47,266 - util.py[WARNING]: 'http://169.254.169.254/2009-04-04/meta-data/instance-id' failed [56/120s]: url error [[Errno 113] No route to host]

2012-08-08 07:34:53,269 - util.py[WARNING]: 'http://169.254.169.254/2009-04-04/meta-data/instance-id' failed [62/120s]: url error [[Errno 113] No route to host]

2012-08-08 07:34:59,274 - util.py[WARNING]: 'http://169.254.169.254/2009-04-04/meta-data/instance-id' failed [68/120s]: url error [[Errno 113] No route to host]

2012-08-08 07:35:06,278 - util.py[WARNING]: 'http://169.254.169.254/2009-04-04/meta-data/instance-id' failed [75/120s]: url error [[Errno 113] No route to host]

2012-08-08 07:35:13,282 - util.py[WARNING]: 'http://169.254.169.254/2009-04-04/meta-data/instance-id' failed [82/120s]: url error [[Errno 113] No route to host]

2012-08-08 07:35:20,285 - util.py[WARNING]: 'http://169.254.169.254/2009-04-04/meta-data/instance-id' failed [89/120s]: url error [[Errno 113] No route to host]

2012-08-08 07:35:27,289 - util.py[WARNING]: 'http://169.254.169.254/2009-04-04/meta-data/instance-id' failed [96/120s]: url error [[Errno 113] No route to host]

2012-08-08 07:35:34,294 - util.py[WARNING]: 'http://169.254.169.254/2009-04-04/meta-data/instance-id' failed [103/120s]: url error [[Errno 113] No route to host]

2012-08-08 07:35:42,297 - util.py[WARNING]: 'http://169.254.169.254/2009-04-04/meta-data/instance-id' failed [111/120s]: url error [[Errno 113] No route to host]

2012-08-08 07:35:50,302 - util.py[WARNING]: 'http://169.254.169.254/2009-04-04/meta-data/instance-id' failed [119/120s]: url error [[Errno 113] No route to host]

2012-08-08 07:35:55,308 - DataSourceEc2.py[CRITICAL]: giving up on md after 124 seconds



no instance data found in start

Skipping profile in /etc/apparmor.d/disable: usr.sbin.rsyslogd


I can see something on the host:
curl http://169.254.169.254:8775/
1.0
2007-01-19
2007-03-01
2007-08-29
2007-10-10
2007-12-15
2008-02-01
2008-09-01
2009-04-04

But doing something like:

I get a HTTP 500 error.

I don't know if the problem is routing or with the meta-data "service".

Any help is appreciated. I'm running this all on one box. Here is my
nova.conf:
--dhcpbridge_flagfile=/etc/nova/nova.conf
--dhcpbridge=/usr/bin/nova-dhcpbridge
--logdir=/var/log/nova
--state_path=/var/lib/nova
--lock_path=/var/lock/nova
--allow_admin_api=true
--use_deprecated_auth=false
--auth_strategy=keystone
--scheduler_driver=nova.scheduler.simple.SimpleScheduler
--s3_host=192.168.1.14
--ec2_host=192.168.1.14
--rabbit_host=192.168.1.14
--cc_host=192.168.1.14
--nova_url=http://192.168.1.14:8774/v1.1/
--routing_source_ip=192.168.1.14
--glance_api_servers=192.168.1.14:9292
--image_service=nova.image.glance.GlanceImageService
--iscsi_ip_prefix=192.168.22
--sql_connection=mysql://nova:s7ack3d@127.0.0.1/nova
--ec2_url=http://192.168.1.14:8773/services/Cloud
--keystone_ec2_url=http://192.168.1.14:5000/v2.0/ec2tokens
--api_paste_config=/etc/nova/api-paste.ini
--libvirt_type=kvm
--libvirt_use_virtio_for_bridges=true
--start_guests_on_host_boot=true
--resume_guests_state_on_host_boot=true
--vnc_enabled=true
--vncproxy_url=http://192.168.1.14:6080
--vnc_console_proxy_url=http://192.168.1.14:6080
# network specific settings
--network_manager=nova.network.manager.FlatDHCPManager
--public_interface=eth0
--flat_interface=eth1
--flat_network_bridge=br100
--fixed_range=10.0.2.0/24
--floating_range=192.168.1.30/27
--network_size=32
--flat_network_dhcp_start=10.0.2.1
--flat_injected=False
--force_dhcp_release
--iscsi_helper=tgtadm
--connection_type=libvirt
--root_helper=sudo nova-rootwrap
--verbose

I have a question about VNC as well, but this is by far more important.

Thanks for your help,

Simon

--
simonsmicrophone.com


_______________________________________________
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help : https://help.launchpad.net/ListHelp
Re: Help with meta-data [ In reply to ]
On 08/08/2012 03:57 AM, Simon Walter wrote:
> Hi all,
>
> I've completed the excruciating Launchpad process of subscribing to a
> mailing list to ask for your help with having my instances access their
> meta-data.

What was excruciating about the subscription process?

> However, they cannot access their meta-data:
>
> Begin: Running /scripts/init-bottom ... done.
> cloud-init start-local running: Wed, 08 Aug 2012 07:33:07 +0000. up 8.32 seconds
> no instance data found in start-local
> ci-info: lo : 1 127.0.0.1 255.0.0.0 .
> ci-info: eth1 : 0 . . fa:16:3e:5a:f3:05
> ci-info: eth0 : 1 192.168.1.205 255.255.255.0 fa:16:3e:23:d7:7c
> ci-info: route-0: 0.0.0.0 192.168.1.1 0.0.0.0 eth0 UG
> ci-info: route-1: 192.168.1.0 0.0.0.0 255.255.255.0 eth0 U
> cloud-init start running: Wed, 08 Aug 2012 07:33:10 +0000. up 11.95 seconds
> 2012-08-08 07:33:54,243 - util.py[WARNING]: 'http://169.254.169.254/2009-04-04/meta-data/instance-id' failed [2/120s]: url error [[Errno 113] No route to host]
<snip>
> 2012-08-08 07:35:55,308 - DataSourceEc2.py[CRITICAL]: giving up on md after 124 seconds
> no instance data found in start
> Skipping profile in /etc/apparmor.d/disable: usr.sbin.rsyslogd
>
> I can see something on the host:
> curl http://169.254.169.254:8775/
> 1.0
> 2007-01-19
> 2007-03-01
> 2007-08-29
> 2007-10-10
> 2007-12-15
> 2008-02-01
> 2008-09-01
> 2009-04-04

Where are you curl'ing from? The compute node or the host running the
nova-ec2-metadata service?

> But doing something like:
>
> I get a HTTP 500 error.

I think you're missing a paste above :) doing something like what?

> I don't know if the problem is routing or with the meta-data "service".

Well, it's unlikely it's an issue with the metadata service because the
metadata service is clearly responding properly to at least ONE host, as
evidenced above. It's more likely a routing issue.

Can you SSH into the VM in question and try pinging the EC2 metadata
service URL? (http://169.254.169.254:8775/)

Best,
-jay

> Any help is appreciated. I'm running this all on one box. Here is my
> nova.conf:
> --dhcpbridge_flagfile=/etc/nova/nova.conf
> --dhcpbridge=/usr/bin/nova-dhcpbridge
> --logdir=/var/log/nova
> --state_path=/var/lib/nova
> --lock_path=/var/lock/nova
> --allow_admin_api=true
> --use_deprecated_auth=false
> --auth_strategy=keystone
> --scheduler_driver=nova.scheduler.simple.SimpleScheduler
> --s3_host=192.168.1.14
> --ec2_host=192.168.1.14
> --rabbit_host=192.168.1.14
> --cc_host=192.168.1.14
> --nova_url=http://192.168.1.14:8774/v1.1/
> --routing_source_ip=192.168.1.14
> --glance_api_servers=192.168.1.14:9292
> --image_service=nova.image.glance.GlanceImageService
> --iscsi_ip_prefix=192.168.22
> --sql_connection=mysql://nova:s7ack3d@127.0.0.1/nova
> --ec2_url=http://192.168.1.14:8773/services/Cloud
> --keystone_ec2_url=http://192.168.1.14:5000/v2.0/ec2tokens
> --api_paste_config=/etc/nova/api-paste.ini
> --libvirt_type=kvm
> --libvirt_use_virtio_for_bridges=true
> --start_guests_on_host_boot=true
> --resume_guests_state_on_host_boot=true
> --vnc_enabled=true
> --vncproxy_url=http://192.168.1.14:6080
> --vnc_console_proxy_url=http://192.168.1.14:6080
> # network specific settings
> --network_manager=nova.network.manager.FlatDHCPManager
> --public_interface=eth0
> --flat_interface=eth1
> --flat_network_bridge=br100
> --fixed_range=10.0.2.0/24
> --floating_range=192.168.1.30/27
> --network_size=32
> --flat_network_dhcp_start=10.0.2.1
> --flat_injected=False
> --force_dhcp_release
> --iscsi_helper=tgtadm
> --connection_type=libvirt
> --root_helper=sudo nova-rootwrap
> --verbose
>
> I have a question about VNC as well, but this is by far more important.
>
> Thanks for your help,
>
> Simon
>

_______________________________________________
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help : https://help.launchpad.net/ListHelp
Re: Help with meta-data [ In reply to ]
On 08/09/2012 06:45 AM, Jay Pipes wrote:
> What was excruciating about the subscription process?

There's many more steps to subscribing to a Launchpad mailing list than
good ol' mailman and the like. I'm just whinging off topic. Sorry...
Thanks for your reply though!

>> However, they cannot access their meta-data:
>>
>> Begin: Running /scripts/init-bottom ... done.
>> cloud-init start-local running: Wed, 08 Aug 2012 07:33:07 +0000. up 8.32 seconds
>> no instance data found in start-local
>> ci-info: lo : 1 127.0.0.1 255.0.0.0 .
>> ci-info: eth1 : 0 . . fa:16:3e:5a:f3:05
>> ci-info: eth0 : 1 192.168.1.205 255.255.255.0 fa:16:3e:23:d7:7c
>> ci-info: route-0: 0.0.0.0 192.168.1.1 0.0.0.0 eth0 UG
>> ci-info: route-1: 192.168.1.0 0.0.0.0 255.255.255.0 eth0 U
>> cloud-init start running: Wed, 08 Aug 2012 07:33:10 +0000. up 11.95 seconds
>> 2012-08-08 07:33:54,243 - util.py[WARNING]: 'http://169.254.169.254/2009-04-04/meta-data/instance-id' failed [2/120s]: url error [[Errno 113] No route to host]
> <snip>
>> 2012-08-08 07:35:55,308 - DataSourceEc2.py[CRITICAL]: giving up on md after 124 seconds
>> no instance data found in start
>> Skipping profile in /etc/apparmor.d/disable: usr.sbin.rsyslogd
>>
>> I can see something on the host:
>> curl http://169.254.169.254:8775/
>> 1.0
>> 2007-01-19
>> 2007-03-01
>> 2007-08-29
>> 2007-10-10
>> 2007-12-15
>> 2008-02-01
>> 2008-09-01
>> 2009-04-04
>
> Where are you curl'ing from? The compute node or the host running the
> nova-ec2-metadata service?

It's all on one box. So the same one I suppose.

>
>> But doing something like:
>>
>> I get a HTTP 500 error.
>
> I think you're missing a paste above :) doing something like what?
>

My bad. Something like:
curl http://169.254.169.254:8775/1.0/
or
curl http://169.254.169.254:8775/2009-04-04/
or
curl http://169.254.169.254:8775/2009-04-04/meta-data/instance-id

Also I notice that the error message above does not contain the port. Is
that normal, or is it really not accessing the correct port?

>> I don't know if the problem is routing or with the meta-data "service".
>
> Well, it's unlikely it's an issue with the metadata service because the
> metadata service is clearly responding properly to at least ONE host, as
> evidenced above. It's more likely a routing issue.
>
> Can you SSH into the VM in question and try pinging the EC2 metadata
> service URL? (http://169.254.169.254:8775/)

I guess I'll have to build a VM from scratch, as I was relying on the
ssh key to be able to ssh into the VM, which apparently is supplied by
the meta-data service.

If that is the case, I can use it without the meta-data service, though
it sure would be nice to have it working properly eventually.

Cheers,

Simon


--
simonsmicrophone.com

_______________________________________________
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help : https://help.launchpad.net/ListHelp
Re: Help with meta-data [ In reply to ]
try adding metadata_host to nova.conf

On Wed, Aug 8, 2012 at 3:57 PM, Simon Walter <simon@gikaku.com> wrote:

>
> Hi all,
>
> I've completed the excruciating Launchpad process of subscribing to a
> mailing list to ask for your help with having my instances access their
> meta-data.
>
> I'm new to OpenStack. So please forgive my n00bness.
>
> I installed OpenStack on Ubuntu 12.04 by following stackgeek's 10 minute
> method and using their scripts: http://stackgeek.com/guides/**
> gettingstarted.html <http://stackgeek.com/guides/gettingstarted.html>
>
> Which got me quite far. I had to fix some of the networking setup. Now I
> can launch instances and ping them.
>
> However, they cannot access their meta-data:
>
> Begin: Running /scripts/init-bottom ... done.
> cloud-init start-local running: Wed, 08 Aug 2012 07:33:07 +0000. up 8.32
> seconds
>
> no instance data found in start-local
>
> ci-info: lo : 1 127.0.0.1 255.0.0.0 .
>
> ci-info: eth1 : 0 . . fa:16:3e:5a:f3:05
>
> ci-info: eth0 : 1 192.168.1.205 255.255.255.0 fa:16:3e:23:d7:7c
>
> ci-info: route-0: 0.0.0.0 192.168.1.1 0.0.0.0 eth0 UG
>
> ci-info: route-1: 192.168.1.0 0.0.0.0 255.255.255.0 eth0 U
>
> cloud-init start running: Wed, 08 Aug 2012 07:33:10 +0000. up 11.95 seconds
>
> 2012-08-08 07:33:54,243 - util.py[WARNING]: 'http://169.254.169.254/2009-*
> *04-04/meta-data/instance-id<http://169.254.169.254/2009-04-04/meta-data/instance-id>'
> failed [2/120s]: url error [[Errno 113] No route to host]
>
> 2012-08-08 07:33:57,242 - util.py[WARNING]: 'http://169.254.169.254/2009-*
> *04-04/meta-data/instance-id<http://169.254.169.254/2009-04-04/meta-data/instance-id>'
> failed [5/120s]: url error [[Errno 113] No route to host]
>
> 2012-08-08 07:34:01,246 - util.py[WARNING]: 'http://169.254.169.254/2009-*
> *04-04/meta-data/instance-id<http://169.254.169.254/2009-04-04/meta-data/instance-id>'
> failed [10/120s]: url error [[Errno 113] No route to host]
>
> 2012-08-08 07:34:04,246 - util.py[WARNING]: 'http://169.254.169.254/2009-*
> *04-04/meta-data/instance-id<http://169.254.169.254/2009-04-04/meta-data/instance-id>'
> failed [13/120s]: url error [[Errno 113] No route to host]
>
> 2012-08-08 07:34:07,246 - util.py[WARNING]: 'http://169.254.169.254/2009-*
> *04-04/meta-data/instance-id<http://169.254.169.254/2009-04-04/meta-data/instance-id>'
> failed [16/120s]: url error [[Errno 113] No route to host]
>
> 2012-08-08 07:34:10,246 - util.py[WARNING]: 'http://169.254.169.254/2009-*
> *04-04/meta-data/instance-id<http://169.254.169.254/2009-04-04/meta-data/instance-id>'
> failed [19/120s]: url error [[Errno 113] No route to host]
>
> 2012-08-08 07:34:13,246 - util.py[WARNING]: 'http://169.254.169.254/2009-*
> *04-04/meta-data/instance-id<http://169.254.169.254/2009-04-04/meta-data/instance-id>'
> failed [22/120s]: url error [[Errno 113] No route to host]
>
> 2012-08-08 07:34:16,246 - util.py[WARNING]: 'http://169.254.169.254/2009-*
> *04-04/meta-data/instance-id<http://169.254.169.254/2009-04-04/meta-data/instance-id>'
> failed [25/120s]: url error [[Errno 113] No route to host]
>
> 2012-08-08 07:34:21,250 - util.py[WARNING]: 'http://169.254.169.254/2009-*
> *04-04/meta-data/instance-id<http://169.254.169.254/2009-04-04/meta-data/instance-id>'
> failed [30/120s]: url error [[Errno 113] No route to host]
>
> 2012-08-08 07:34:24,250 - util.py[WARNING]: 'http://169.254.169.254/2009-*
> *04-04/meta-data/instance-id<http://169.254.169.254/2009-04-04/meta-data/instance-id>'
> failed [33/120s]: url error [[Errno 113] No route to host]
>
> 2012-08-08 07:34:29,254 - util.py[WARNING]: 'http://169.254.169.254/2009-*
> *04-04/meta-data/instance-id<http://169.254.169.254/2009-04-04/meta-data/instance-id>'
> failed [38/120s]: url error [[Errno 113] No route to host]
>
> 2012-08-08 07:34:35,258 - util.py[WARNING]: 'http://169.254.169.254/2009-*
> *04-04/meta-data/instance-id<http://169.254.169.254/2009-04-04/meta-data/instance-id>'
> failed [44/120s]: url error [[Errno 113] No route to host]
>
> 2012-08-08 07:34:41,261 - util.py[WARNING]: 'http://169.254.169.254/2009-*
> *04-04/meta-data/instance-id<http://169.254.169.254/2009-04-04/meta-data/instance-id>'
> failed [50/120s]: url error [[Errno 113] No route to host]
>
> 2012-08-08 07:34:47,266 - util.py[WARNING]: 'http://169.254.169.254/2009-*
> *04-04/meta-data/instance-id<http://169.254.169.254/2009-04-04/meta-data/instance-id>'
> failed [56/120s]: url error [[Errno 113] No route to host]
>
> 2012-08-08 07:34:53,269 - util.py[WARNING]: 'http://169.254.169.254/2009-*
> *04-04/meta-data/instance-id<http://169.254.169.254/2009-04-04/meta-data/instance-id>'
> failed [62/120s]: url error [[Errno 113] No route to host]
>
> 2012-08-08 07:34:59,274 - util.py[WARNING]: 'http://169.254.169.254/2009-*
> *04-04/meta-data/instance-id<http://169.254.169.254/2009-04-04/meta-data/instance-id>'
> failed [68/120s]: url error [[Errno 113] No route to host]
>
> 2012-08-08 07:35:06,278 - util.py[WARNING]: 'http://169.254.169.254/2009-*
> *04-04/meta-data/instance-id<http://169.254.169.254/2009-04-04/meta-data/instance-id>'
> failed [75/120s]: url error [[Errno 113] No route to host]
>
> 2012-08-08 07:35:13,282 - util.py[WARNING]: 'http://169.254.169.254/2009-*
> *04-04/meta-data/instance-id<http://169.254.169.254/2009-04-04/meta-data/instance-id>'
> failed [82/120s]: url error [[Errno 113] No route to host]
>
> 2012-08-08 07:35:20,285 - util.py[WARNING]: 'http://169.254.169.254/2009-*
> *04-04/meta-data/instance-id<http://169.254.169.254/2009-04-04/meta-data/instance-id>'
> failed [89/120s]: url error [[Errno 113] No route to host]
>
> 2012-08-08 07:35:27,289 - util.py[WARNING]: 'http://169.254.169.254/2009-*
> *04-04/meta-data/instance-id<http://169.254.169.254/2009-04-04/meta-data/instance-id>'
> failed [96/120s]: url error [[Errno 113] No route to host]
>
> 2012-08-08 07:35:34,294 - util.py[WARNING]: 'http://169.254.169.254/2009-*
> *04-04/meta-data/instance-id<http://169.254.169.254/2009-04-04/meta-data/instance-id>'
> failed [103/120s]: url error [[Errno 113] No route to host]
>
> 2012-08-08 07:35:42,297 - util.py[WARNING]: 'http://169.254.169.254/2009-*
> *04-04/meta-data/instance-id<http://169.254.169.254/2009-04-04/meta-data/instance-id>'
> failed [111/120s]: url error [[Errno 113] No route to host]
>
> 2012-08-08 07:35:50,302 - util.py[WARNING]: 'http://169.254.169.254/2009-*
> *04-04/meta-data/instance-id<http://169.254.169.254/2009-04-04/meta-data/instance-id>'
> failed [119/120s]: url error [[Errno 113] No route to host]
>
> 2012-08-08 07:35:55,308 - DataSourceEc2.py[CRITICAL]: giving up on md
> after 124 seconds
>
>
>
> no instance data found in start
>
> Skipping profile in /etc/apparmor.d/disable: usr.sbin.rsyslogd
>
>
> I can see something on the host:
> curl http://169.254.169.254:8775/
> 1.0
> 2007-01-19
> 2007-03-01
> 2007-08-29
> 2007-10-10
> 2007-12-15
> 2008-02-01
> 2008-09-01
> 2009-04-04
>
> But doing something like:
>
> I get a HTTP 500 error.
>
> I don't know if the problem is routing or with the meta-data "service".
>
> Any help is appreciated. I'm running this all on one box. Here is my
> nova.conf:
> --dhcpbridge_flagfile=/etc/**nova/nova.conf
> --dhcpbridge=/usr/bin/nova-**dhcpbridge
> --logdir=/var/log/nova
> --state_path=/var/lib/nova
> --lock_path=/var/lock/nova
> --allow_admin_api=true
> --use_deprecated_auth=false
> --auth_strategy=keystone
> --scheduler_driver=nova.**scheduler.simple.**SimpleScheduler
> --s3_host=192.168.1.14
> --ec2_host=192.168.1.14
> --rabbit_host=192.168.1.14
> --cc_host=192.168.1.14
> --nova_url=http://192.168.1.**14:8774/v1.1/<http://192.168.1.14:8774/v1.1/>
> --routing_source_ip=192.168.1.**14
> --glance_api_servers=192.168.**1.14:9292 <http://192.168.1.14:9292>
> --image_service=nova.image.**glance.GlanceImageService
> --iscsi_ip_prefix=192.168.22
> --sql_connection=mysql://nova:**s7ack3d@127.0.0.1/nova<http://nova:s7ack3d@127.0.0.1/nova>
> --ec2_url=http://192.168.1.14:**8773/services/Cloud<http://192.168.1.14:8773/services/Cloud>
> --keystone_ec2_url=http://192.**168.1.14:5000/v2.0/ec2tokens<http://192.168.1.14:5000/v2.0/ec2tokens>
> --api_paste_config=/etc/nova/**api-paste.ini
> --libvirt_type=kvm
> --libvirt_use_virtio_for_**bridges=true
> --start_guests_on_host_boot=**true
> --resume_guests_state_on_host_**boot=true
> --vnc_enabled=true
> --vncproxy_url=http://192.168.**1.14:6080 <http://192.168.1.14:6080>
> --vnc_console_proxy_url=http:/**/192.168.1.14:6080<http://192.168.1.14:6080>
> # network specific settings
> --network_manager=nova.**network.manager.**FlatDHCPManager
> --public_interface=eth0
> --flat_interface=eth1
> --flat_network_bridge=br100
> --fixed_range=10.0.2.0/24
> --floating_range=192.168.1.30/**27 <http://192.168.1.30/27>
> --network_size=32
> --flat_network_dhcp_start=10.**0.2.1
> --flat_injected=False
> --force_dhcp_release
> --iscsi_helper=tgtadm
> --connection_type=libvirt
> --root_helper=sudo nova-rootwrap
> --verbose
>
> I have a question about VNC as well, but this is by far more important.
>
> Thanks for your help,
>
> Simon
>
> --
> simonsmicrophone.com
>
>
> ______________________________**_________________
> Mailing list: https://launchpad.net/~**openstack<https://launchpad.net/~openstack>
> Post to : openstack@lists.launchpad.net
> Unsubscribe : https://launchpad.net/~**openstack<https://launchpad.net/~openstack>
> More help : https://help.launchpad.net/**ListHelp<https://help.launchpad.net/ListHelp>
>
Re: Help with meta-data [ In reply to ]
On 08/09/2012 01:11 PM, tacy lee wrote:
> try adding metadata_host to nova.conf

The thing is the iptable rules have 169.254.169.254 NATed correctly. So
the address is correct. It's just that the VMs cannot access it.


--
simonsmicrophone.com

_______________________________________________
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help : https://help.launchpad.net/ListHelp
Re: Help with meta-data [ In reply to ]
On 08/09/2012 12:59 PM, Scott Moser wrote:
> On Aug 8, 2012, at 8:20 PM, "Simon Walter" <simon@gikaku.com> wrote:
>
>>
>> On 08/09/2012 06:45 AM, Jay Pipes
>> I guess I'll have to build a VM from scratch, as I was relying on the ssh key to be able to ssh into the VM, which apparently is supplied by the meta-data service.
>>
> use cirros.
> load an image, ssh on with 'cirros' user. pass is 'cubswin:)'

Thank you. That was good advice.

Somehow I was not able to connect via ssh. I managed to get novnc
working and logged into the VM. I can't find anything about connecting
via serial or the like as you can with Xen. I need to read more about
KVM I guess.

Anyway, I think my networking setup is stuffed. I thought the "10
minutes" install would be the quickest way to get and running. Now I
find myself pouring over documentation trying to understand how best to
setup FlatDHCPManager with two network interfaces. I understand many
things have changed. So I don't want to go reading something out of
date. I found these blog posts which explained a lot:
http://www.mirantis.com/blog/openstack-networking-flatmanager-and-flatdhcpmanager/#comments
http://www.mirantis.com/blog/openstack-networking-single-host-flatdhcpmanager/
But am I reading the wrong thing? I like the way Stackgeek had it set up:
http://stackgeek.com/guides/gettingstarted.html

But I think they are missing details or it's out dated. For example,
with their setup the vnc console in horizon does not work because
nova-vncproxy is installed rather than novnc.

I'm pretty sure I can figure the networking out if I have the right
documentation in the first place. Is there a clear instructions for this
anywhere? Or would someone mind walking me through it again. So far I've
followed the stackgeek setup above, but the networking is obviously stuffed.

Must I have the flat_interface in promiscuous mode?
Or does it actually need an IP address?
Why are my VMs picking up an IP address from the public_interface DHCP
server and not from the flat_network_bridge?

Too many questions to ask. So I thought I should just ask: what is
missing or incorrect from Stackgeeks 10 minute scripts?

Many thanks for any advice, tips, docs, etc.

Cheers,

Simon


--
simonsmicrophone.com

_______________________________________________
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help : https://help.launchpad.net/ListHelp
Re: Help with meta-data [ In reply to ]
All, sorry for top posting, but this is a fine example of why we
really need bloggers to help with the documentation. These fragmented
instructions are difficult to rely on - we need maintainable,
process-oriented treatment of content.

Mirantis peeps, you have added in your blog entries to the docs in the
past, let's find ways to continually do that and maintain going
forward.

I'm not so interested in more install guides, but definitely
interested in more configuration guides. So Kord, while I like the
idea (and execution!) of the StackGeek 10-minute guide, it's not one
to bring into the official docs. But we would definitely welcome your
reviews of incoming updates to the docs!

Thanks Simon for bringing your difficulties to the list - we
continually work on improving the docs. What you learn now could help
hundreds if not thousands of others, so I'd love for you to improve
the official docs with your findings.
Thanks,
Anne

On Thu, Aug 9, 2012 at 4:42 AM, Simon Walter <simon@gikaku.com> wrote:
>
> On 08/09/2012 12:59 PM, Scott Moser wrote:
>>
>> On Aug 8, 2012, at 8:20 PM, "Simon Walter" <simon@gikaku.com> wrote:
>>
>>>
>>> On 08/09/2012 06:45 AM, Jay Pipes
>>> I guess I'll have to build a VM from scratch, as I was relying on the ssh
>>> key to be able to ssh into the VM, which apparently is supplied by the
>>> meta-data service.
>>>
>> use cirros.
>> load an image, ssh on with 'cirros' user. pass is 'cubswin:)'
>
>
> Thank you. That was good advice.
>
> Somehow I was not able to connect via ssh. I managed to get novnc working
> and logged into the VM. I can't find anything about connecting via serial or
> the like as you can with Xen. I need to read more about KVM I guess.
>
> Anyway, I think my networking setup is stuffed. I thought the "10 minutes"
> install would be the quickest way to get and running. Now I find myself
> pouring over documentation trying to understand how best to setup
> FlatDHCPManager with two network interfaces. I understand many things have
> changed. So I don't want to go reading something out of date. I found these
> blog posts which explained a lot:
> http://www.mirantis.com/blog/openstack-networking-flatmanager-and-flatdhcpmanager/#comments
> http://www.mirantis.com/blog/openstack-networking-single-host-flatdhcpmanager/
> But am I reading the wrong thing? I like the way Stackgeek had it set up:
> http://stackgeek.com/guides/gettingstarted.html
>
> But I think they are missing details or it's out dated. For example, with
> their setup the vnc console in horizon does not work because nova-vncproxy
> is installed rather than novnc.
>
> I'm pretty sure I can figure the networking out if I have the right
> documentation in the first place. Is there a clear instructions for this
> anywhere? Or would someone mind walking me through it again. So far I've
> followed the stackgeek setup above, but the networking is obviously stuffed.
>
> Must I have the flat_interface in promiscuous mode?
> Or does it actually need an IP address?
> Why are my VMs picking up an IP address from the public_interface DHCP
> server and not from the flat_network_bridge?
>
> Too many questions to ask. So I thought I should just ask: what is missing
> or incorrect from Stackgeeks 10 minute scripts?
>
> Many thanks for any advice, tips, docs, etc.
>
>
> Cheers,
>
> Simon
>
>
> --
> simonsmicrophone.com
>
> _______________________________________________
> Mailing list: https://launchpad.net/~openstack
> Post to : openstack@lists.launchpad.net
> Unsubscribe : https://launchpad.net/~openstack
> More help : https://help.launchpad.net/ListHelp

_______________________________________________
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help : https://help.launchpad.net/ListHelp
Re: Help with meta-data [ In reply to ]
Hi Anne,

I accidentally found this email of yours while looking for links to my post.
I'd probably have found it earlier if you cc'd me on
ekirpichov@gmail.com or ekirpichev@mirantis.com [yes, that's two
different spellings...] :)

I support the idea that this should be somehow integrated in the docs,
but I'm not sure where exactly in the docs is a good place for
information of this style. Would it help if I just linked to the posts
from some wiki page or from the docs? Or would it only help if I (or
somebody) actually merged the relevant parts of the posts into
official documentation?

On Thu, Aug 9, 2012 at 8:07 AM, Anne Gentle <anne@openstack.org> wrote:
> All, sorry for top posting, but this is a fine example of why we
> really need bloggers to help with the documentation. These fragmented
> instructions are difficult to rely on - we need maintainable,
> process-oriented treatment of content.
>
> Mirantis peeps, you have added in your blog entries to the docs in the
> past, let's find ways to continually do that and maintain going
> forward.
>
> I'm not so interested in more install guides, but definitely
> interested in more configuration guides. So Kord, while I like the
> idea (and execution!) of the StackGeek 10-minute guide, it's not one
> to bring into the official docs. But we would definitely welcome your
> reviews of incoming updates to the docs!
>
> Thanks Simon for bringing your difficulties to the list - we
> continually work on improving the docs. What you learn now could help
> hundreds if not thousands of others, so I'd love for you to improve
> the official docs with your findings.
> Thanks,
> Anne
>
> On Thu, Aug 9, 2012 at 4:42 AM, Simon Walter <simon@gikaku.com> wrote:
>>
>> On 08/09/2012 12:59 PM, Scott Moser wrote:
>>>
>>> On Aug 8, 2012, at 8:20 PM, "Simon Walter" <simon@gikaku.com> wrote:
>>>
>>>>
>>>> On 08/09/2012 06:45 AM, Jay Pipes
>>>> I guess I'll have to build a VM from scratch, as I was relying on the ssh
>>>> key to be able to ssh into the VM, which apparently is supplied by the
>>>> meta-data service.
>>>>
>>> use cirros.
>>> load an image, ssh on with 'cirros' user. pass is 'cubswin:)'
>>
>>
>> Thank you. That was good advice.
>>
>> Somehow I was not able to connect via ssh. I managed to get novnc working
>> and logged into the VM. I can't find anything about connecting via serial or
>> the like as you can with Xen. I need to read more about KVM I guess.
>>
>> Anyway, I think my networking setup is stuffed. I thought the "10 minutes"
>> install would be the quickest way to get and running. Now I find myself
>> pouring over documentation trying to understand how best to setup
>> FlatDHCPManager with two network interfaces. I understand many things have
>> changed. So I don't want to go reading something out of date. I found these
>> blog posts which explained a lot:
>> http://www.mirantis.com/blog/openstack-networking-flatmanager-and-flatdhcpmanager/#comments
>> http://www.mirantis.com/blog/openstack-networking-single-host-flatdhcpmanager/
>> But am I reading the wrong thing? I like the way Stackgeek had it set up:
>> http://stackgeek.com/guides/gettingstarted.html
>>
>> But I think they are missing details or it's out dated. For example, with
>> their setup the vnc console in horizon does not work because nova-vncproxy
>> is installed rather than novnc.
>>
>> I'm pretty sure I can figure the networking out if I have the right
>> documentation in the first place. Is there a clear instructions for this
>> anywhere? Or would someone mind walking me through it again. So far I've
>> followed the stackgeek setup above, but the networking is obviously stuffed.
>>
>> Must I have the flat_interface in promiscuous mode?
>> Or does it actually need an IP address?
>> Why are my VMs picking up an IP address from the public_interface DHCP
>> server and not from the flat_network_bridge?
>>
>> Too many questions to ask. So I thought I should just ask: what is missing
>> or incorrect from Stackgeeks 10 minute scripts?
>>
>> Many thanks for any advice, tips, docs, etc.
>>
>>
>> Cheers,
>>
>> Simon
>>
>>
>> --
>> simonsmicrophone.com
>>
>> _______________________________________________
>> Mailing list: https://launchpad.net/~openstack
>> Post to : openstack@lists.launchpad.net
>> Unsubscribe : https://launchpad.net/~openstack
>> More help : https://help.launchpad.net/ListHelp
>
> _______________________________________________
> Mailing list: https://launchpad.net/~openstack
> Post to : openstack@lists.launchpad.net
> Unsubscribe : https://launchpad.net/~openstack
> More help : https://help.launchpad.net/ListHelp



--
Eugene Kirpichov
http://www.linkedin.com/in/eugenekirpichov

_______________________________________________
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help : https://help.launchpad.net/ListHelp
Re: Help with meta-data [ In reply to ]
Hi Eugene -
But I thought "everyone" was on the openstack list! :) Thanks for following up.

On Wed, Aug 15, 2012 at 4:35 PM, Eugene Kirpichov <ekirpichov@gmail.com> wrote:
> Hi Anne,
>
> I accidentally found this email of yours while looking for links to my post.
> I'd probably have found it earlier if you cc'd me on
> ekirpichov@gmail.com or ekirpichev@mirantis.com [yes, that's two
> different spellings...] :)
>
> I support the idea that this should be somehow integrated in the docs,
> but I'm not sure where exactly in the docs is a good place for
> information of this style. Would it help if I just linked to the posts
> from some wiki page or from the docs?

I do like to put relevant blog posts on the wiki at
http://wiki.openstack.org/BloggersTips, so you can certainly add to
that page. If it's really missing information in the docs, though, it
should be added to the docs. I know that's a tough judgement call but
we all have to encourage that call.

Or would it only help if I (or
> somebody) actually merged the relevant parts of the posts into
> official documentation?

I wouldn't say "only help" but I prefer that you merge the relevant
parts of the posts. It's tougher for a doc team member to merge only
parts in without violating the license of the content - you as content
owner can certainly choose which parts to move into the official
documentation though.

Thanks for asking for clarifications - these are certainly gray areas
that I'd like to shine light upon.
Anne

> On Thu, Aug 9, 2012 at 8:07 AM, Anne Gentle <anne@openstack.org> wrote:
>> All, sorry for top posting, but this is a fine example of why we
>> really need bloggers to help with the documentation. These fragmented
>> instructions are difficult to rely on - we need maintainable,
>> process-oriented treatment of content.
>>
>> Mirantis peeps, you have added in your blog entries to the docs in the
>> past, let's find ways to continually do that and maintain going
>> forward.
>>
>> I'm not so interested in more install guides, but definitely
>> interested in more configuration guides. So Kord, while I like the
>> idea (and execution!) of the StackGeek 10-minute guide, it's not one
>> to bring into the official docs. But we would definitely welcome your
>> reviews of incoming updates to the docs!
>>
>> Thanks Simon for bringing your difficulties to the list - we
>> continually work on improving the docs. What you learn now could help
>> hundreds if not thousands of others, so I'd love for you to improve
>> the official docs with your findings.
>> Thanks,
>> Anne
>>
>> On Thu, Aug 9, 2012 at 4:42 AM, Simon Walter <simon@gikaku.com> wrote:
>>>
>>> On 08/09/2012 12:59 PM, Scott Moser wrote:
>>>>
>>>> On Aug 8, 2012, at 8:20 PM, "Simon Walter" <simon@gikaku.com> wrote:
>>>>
>>>>>
>>>>> On 08/09/2012 06:45 AM, Jay Pipes
>>>>> I guess I'll have to build a VM from scratch, as I was relying on the ssh
>>>>> key to be able to ssh into the VM, which apparently is supplied by the
>>>>> meta-data service.
>>>>>
>>>> use cirros.
>>>> load an image, ssh on with 'cirros' user. pass is 'cubswin:)'
>>>
>>>
>>> Thank you. That was good advice.
>>>
>>> Somehow I was not able to connect via ssh. I managed to get novnc working
>>> and logged into the VM. I can't find anything about connecting via serial or
>>> the like as you can with Xen. I need to read more about KVM I guess.
>>>
>>> Anyway, I think my networking setup is stuffed. I thought the "10 minutes"
>>> install would be the quickest way to get and running. Now I find myself
>>> pouring over documentation trying to understand how best to setup
>>> FlatDHCPManager with two network interfaces. I understand many things have
>>> changed. So I don't want to go reading something out of date. I found these
>>> blog posts which explained a lot:
>>> http://www.mirantis.com/blog/openstack-networking-flatmanager-and-flatdhcpmanager/#comments
>>> http://www.mirantis.com/blog/openstack-networking-single-host-flatdhcpmanager/
>>> But am I reading the wrong thing? I like the way Stackgeek had it set up:
>>> http://stackgeek.com/guides/gettingstarted.html
>>>
>>> But I think they are missing details or it's out dated. For example, with
>>> their setup the vnc console in horizon does not work because nova-vncproxy
>>> is installed rather than novnc.
>>>
>>> I'm pretty sure I can figure the networking out if I have the right
>>> documentation in the first place. Is there a clear instructions for this
>>> anywhere? Or would someone mind walking me through it again. So far I've
>>> followed the stackgeek setup above, but the networking is obviously stuffed.
>>>
>>> Must I have the flat_interface in promiscuous mode?
>>> Or does it actually need an IP address?
>>> Why are my VMs picking up an IP address from the public_interface DHCP
>>> server and not from the flat_network_bridge?
>>>
>>> Too many questions to ask. So I thought I should just ask: what is missing
>>> or incorrect from Stackgeeks 10 minute scripts?
>>>
>>> Many thanks for any advice, tips, docs, etc.
>>>
>>>
>>> Cheers,
>>>
>>> Simon
>>>
>>>
>>> --
>>> simonsmicrophone.com
>>>
>>> _______________________________________________
>>> Mailing list: https://launchpad.net/~openstack
>>> Post to : openstack@lists.launchpad.net
>>> Unsubscribe : https://launchpad.net/~openstack
>>> More help : https://help.launchpad.net/ListHelp
>>
>> _______________________________________________
>> Mailing list: https://launchpad.net/~openstack
>> Post to : openstack@lists.launchpad.net
>> Unsubscribe : https://launchpad.net/~openstack
>> More help : https://help.launchpad.net/ListHelp
>
>
>
> --
> Eugene Kirpichov
> http://www.linkedin.com/in/eugenekirpichov

_______________________________________________
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help : https://help.launchpad.net/ListHelp
Re: Help with meta-data [ In reply to ]
Hi Anne,

On Wed, Aug 15, 2012 at 2:55 PM, Anne Gentle <anne@openstack.org> wrote:
> Hi Eugene -
> But I thought "everyone" was on the openstack list! :) Thanks for following up.
>
> On Wed, Aug 15, 2012 at 4:35 PM, Eugene Kirpichov <ekirpichov@gmail.com> wrote:
>> Hi Anne,
>>
>> I accidentally found this email of yours while looking for links to my post.
>> I'd probably have found it earlier if you cc'd me on
>> ekirpichov@gmail.com or ekirpichev@mirantis.com [yes, that's two
>> different spellings...] :)
>>
>> I support the idea that this should be somehow integrated in the docs,
>> but I'm not sure where exactly in the docs is a good place for
>> information of this style. Would it help if I just linked to the posts
>> from some wiki page or from the docs?
>
> I do like to put relevant blog posts on the wiki at
> http://wiki.openstack.org/BloggersTips, so you can certainly add to
> that page. If it's really missing information in the docs, though, it
> should be added to the docs. I know that's a tough judgement call but
> we all have to encourage that call.

Thanks. I added a link to the post to this wiki page and I'll now
spend some time picking what to integrate into the docs.

>
> Or would it only help if I (or
>> somebody) actually merged the relevant parts of the posts into
>> official documentation?
>
> I wouldn't say "only help" but I prefer that you merge the relevant
> parts of the posts. It's tougher for a doc team member to merge only
> parts in without violating the license of the content - you as content
> owner can certainly choose which parts to move into the official
> documentation though.
>
> Thanks for asking for clarifications - these are certainly gray areas
> that I'd like to shine light upon.
> Anne
>
>> On Thu, Aug 9, 2012 at 8:07 AM, Anne Gentle <anne@openstack.org> wrote:
>>> All, sorry for top posting, but this is a fine example of why we
>>> really need bloggers to help with the documentation. These fragmented
>>> instructions are difficult to rely on - we need maintainable,
>>> process-oriented treatment of content.
>>>
>>> Mirantis peeps, you have added in your blog entries to the docs in the
>>> past, let's find ways to continually do that and maintain going
>>> forward.
>>>
>>> I'm not so interested in more install guides, but definitely
>>> interested in more configuration guides. So Kord, while I like the
>>> idea (and execution!) of the StackGeek 10-minute guide, it's not one
>>> to bring into the official docs. But we would definitely welcome your
>>> reviews of incoming updates to the docs!
>>>
>>> Thanks Simon for bringing your difficulties to the list - we
>>> continually work on improving the docs. What you learn now could help
>>> hundreds if not thousands of others, so I'd love for you to improve
>>> the official docs with your findings.
>>> Thanks,
>>> Anne
>>>
>>> On Thu, Aug 9, 2012 at 4:42 AM, Simon Walter <simon@gikaku.com> wrote:
>>>>
>>>> On 08/09/2012 12:59 PM, Scott Moser wrote:
>>>>>
>>>>> On Aug 8, 2012, at 8:20 PM, "Simon Walter" <simon@gikaku.com> wrote:
>>>>>
>>>>>>
>>>>>> On 08/09/2012 06:45 AM, Jay Pipes
>>>>>> I guess I'll have to build a VM from scratch, as I was relying on the ssh
>>>>>> key to be able to ssh into the VM, which apparently is supplied by the
>>>>>> meta-data service.
>>>>>>
>>>>> use cirros.
>>>>> load an image, ssh on with 'cirros' user. pass is 'cubswin:)'
>>>>
>>>>
>>>> Thank you. That was good advice.
>>>>
>>>> Somehow I was not able to connect via ssh. I managed to get novnc working
>>>> and logged into the VM. I can't find anything about connecting via serial or
>>>> the like as you can with Xen. I need to read more about KVM I guess.
>>>>
>>>> Anyway, I think my networking setup is stuffed. I thought the "10 minutes"
>>>> install would be the quickest way to get and running. Now I find myself
>>>> pouring over documentation trying to understand how best to setup
>>>> FlatDHCPManager with two network interfaces. I understand many things have
>>>> changed. So I don't want to go reading something out of date. I found these
>>>> blog posts which explained a lot:
>>>> http://www.mirantis.com/blog/openstack-networking-flatmanager-and-flatdhcpmanager/#comments
>>>> http://www.mirantis.com/blog/openstack-networking-single-host-flatdhcpmanager/
>>>> But am I reading the wrong thing? I like the way Stackgeek had it set up:
>>>> http://stackgeek.com/guides/gettingstarted.html
>>>>
>>>> But I think they are missing details or it's out dated. For example, with
>>>> their setup the vnc console in horizon does not work because nova-vncproxy
>>>> is installed rather than novnc.
>>>>
>>>> I'm pretty sure I can figure the networking out if I have the right
>>>> documentation in the first place. Is there a clear instructions for this
>>>> anywhere? Or would someone mind walking me through it again. So far I've
>>>> followed the stackgeek setup above, but the networking is obviously stuffed.
>>>>
>>>> Must I have the flat_interface in promiscuous mode?
>>>> Or does it actually need an IP address?
>>>> Why are my VMs picking up an IP address from the public_interface DHCP
>>>> server and not from the flat_network_bridge?
>>>>
>>>> Too many questions to ask. So I thought I should just ask: what is missing
>>>> or incorrect from Stackgeeks 10 minute scripts?
>>>>
>>>> Many thanks for any advice, tips, docs, etc.
>>>>
>>>>
>>>> Cheers,
>>>>
>>>> Simon
>>>>
>>>>
>>>> --
>>>> simonsmicrophone.com
>>>>
>>>> _______________________________________________
>>>> Mailing list: https://launchpad.net/~openstack
>>>> Post to : openstack@lists.launchpad.net
>>>> Unsubscribe : https://launchpad.net/~openstack
>>>> More help : https://help.launchpad.net/ListHelp
>>>
>>> _______________________________________________
>>> Mailing list: https://launchpad.net/~openstack
>>> Post to : openstack@lists.launchpad.net
>>> Unsubscribe : https://launchpad.net/~openstack
>>> More help : https://help.launchpad.net/ListHelp
>>
>>
>>
>> --
>> Eugene Kirpichov
>> http://www.linkedin.com/in/eugenekirpichov



--
Eugene Kirpichov
http://www.linkedin.com/in/eugenekirpichov

_______________________________________________
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help : https://help.launchpad.net/ListHelp
Re: Help with meta-data [ In reply to ]
I added some documentation.
Submitted for review here https://review.openstack.org/#/c/11518/

On Thu, Aug 16, 2012 at 4:10 PM, Eugene Kirpichov <ekirpichov@gmail.com> wrote:
> Hi Anne,
>
> On Wed, Aug 15, 2012 at 2:55 PM, Anne Gentle <anne@openstack.org> wrote:
>> Hi Eugene -
>> But I thought "everyone" was on the openstack list! :) Thanks for following up.
>>
>> On Wed, Aug 15, 2012 at 4:35 PM, Eugene Kirpichov <ekirpichov@gmail.com> wrote:
>>> Hi Anne,
>>>
>>> I accidentally found this email of yours while looking for links to my post.
>>> I'd probably have found it earlier if you cc'd me on
>>> ekirpichov@gmail.com or ekirpichev@mirantis.com [yes, that's two
>>> different spellings...] :)
>>>
>>> I support the idea that this should be somehow integrated in the docs,
>>> but I'm not sure where exactly in the docs is a good place for
>>> information of this style. Would it help if I just linked to the posts
>>> from some wiki page or from the docs?
>>
>> I do like to put relevant blog posts on the wiki at
>> http://wiki.openstack.org/BloggersTips, so you can certainly add to
>> that page. If it's really missing information in the docs, though, it
>> should be added to the docs. I know that's a tough judgement call but
>> we all have to encourage that call.
>
> Thanks. I added a link to the post to this wiki page and I'll now
> spend some time picking what to integrate into the docs.
>
>>
>> Or would it only help if I (or
>>> somebody) actually merged the relevant parts of the posts into
>>> official documentation?
>>
>> I wouldn't say "only help" but I prefer that you merge the relevant
>> parts of the posts. It's tougher for a doc team member to merge only
>> parts in without violating the license of the content - you as content
>> owner can certainly choose which parts to move into the official
>> documentation though.
>>
>> Thanks for asking for clarifications - these are certainly gray areas
>> that I'd like to shine light upon.
>> Anne
>>
>>> On Thu, Aug 9, 2012 at 8:07 AM, Anne Gentle <anne@openstack.org> wrote:
>>>> All, sorry for top posting, but this is a fine example of why we
>>>> really need bloggers to help with the documentation. These fragmented
>>>> instructions are difficult to rely on - we need maintainable,
>>>> process-oriented treatment of content.
>>>>
>>>> Mirantis peeps, you have added in your blog entries to the docs in the
>>>> past, let's find ways to continually do that and maintain going
>>>> forward.
>>>>
>>>> I'm not so interested in more install guides, but definitely
>>>> interested in more configuration guides. So Kord, while I like the
>>>> idea (and execution!) of the StackGeek 10-minute guide, it's not one
>>>> to bring into the official docs. But we would definitely welcome your
>>>> reviews of incoming updates to the docs!
>>>>
>>>> Thanks Simon for bringing your difficulties to the list - we
>>>> continually work on improving the docs. What you learn now could help
>>>> hundreds if not thousands of others, so I'd love for you to improve
>>>> the official docs with your findings.
>>>> Thanks,
>>>> Anne
>>>>
>>>> On Thu, Aug 9, 2012 at 4:42 AM, Simon Walter <simon@gikaku.com> wrote:
>>>>>
>>>>> On 08/09/2012 12:59 PM, Scott Moser wrote:
>>>>>>
>>>>>> On Aug 8, 2012, at 8:20 PM, "Simon Walter" <simon@gikaku.com> wrote:
>>>>>>
>>>>>>>
>>>>>>> On 08/09/2012 06:45 AM, Jay Pipes
>>>>>>> I guess I'll have to build a VM from scratch, as I was relying on the ssh
>>>>>>> key to be able to ssh into the VM, which apparently is supplied by the
>>>>>>> meta-data service.
>>>>>>>
>>>>>> use cirros.
>>>>>> load an image, ssh on with 'cirros' user. pass is 'cubswin:)'
>>>>>
>>>>>
>>>>> Thank you. That was good advice.
>>>>>
>>>>> Somehow I was not able to connect via ssh. I managed to get novnc working
>>>>> and logged into the VM. I can't find anything about connecting via serial or
>>>>> the like as you can with Xen. I need to read more about KVM I guess.
>>>>>
>>>>> Anyway, I think my networking setup is stuffed. I thought the "10 minutes"
>>>>> install would be the quickest way to get and running. Now I find myself
>>>>> pouring over documentation trying to understand how best to setup
>>>>> FlatDHCPManager with two network interfaces. I understand many things have
>>>>> changed. So I don't want to go reading something out of date. I found these
>>>>> blog posts which explained a lot:
>>>>> http://www.mirantis.com/blog/openstack-networking-flatmanager-and-flatdhcpmanager/#comments
>>>>> http://www.mirantis.com/blog/openstack-networking-single-host-flatdhcpmanager/
>>>>> But am I reading the wrong thing? I like the way Stackgeek had it set up:
>>>>> http://stackgeek.com/guides/gettingstarted.html
>>>>>
>>>>> But I think they are missing details or it's out dated. For example, with
>>>>> their setup the vnc console in horizon does not work because nova-vncproxy
>>>>> is installed rather than novnc.
>>>>>
>>>>> I'm pretty sure I can figure the networking out if I have the right
>>>>> documentation in the first place. Is there a clear instructions for this
>>>>> anywhere? Or would someone mind walking me through it again. So far I've
>>>>> followed the stackgeek setup above, but the networking is obviously stuffed.
>>>>>
>>>>> Must I have the flat_interface in promiscuous mode?
>>>>> Or does it actually need an IP address?
>>>>> Why are my VMs picking up an IP address from the public_interface DHCP
>>>>> server and not from the flat_network_bridge?
>>>>>
>>>>> Too many questions to ask. So I thought I should just ask: what is missing
>>>>> or incorrect from Stackgeeks 10 minute scripts?
>>>>>
>>>>> Many thanks for any advice, tips, docs, etc.
>>>>>
>>>>>
>>>>> Cheers,
>>>>>
>>>>> Simon
>>>>>
>>>>>
>>>>> --
>>>>> simonsmicrophone.com
>>>>>
>>>>> _______________________________________________
>>>>> Mailing list: https://launchpad.net/~openstack
>>>>> Post to : openstack@lists.launchpad.net
>>>>> Unsubscribe : https://launchpad.net/~openstack
>>>>> More help : https://help.launchpad.net/ListHelp
>>>>
>>>> _______________________________________________
>>>> Mailing list: https://launchpad.net/~openstack
>>>> Post to : openstack@lists.launchpad.net
>>>> Unsubscribe : https://launchpad.net/~openstack
>>>> More help : https://help.launchpad.net/ListHelp
>>>
>>>
>>>
>>> --
>>> Eugene Kirpichov
>>> http://www.linkedin.com/in/eugenekirpichov
>
>
>
> --
> Eugene Kirpichov
> http://www.linkedin.com/in/eugenekirpichov



--
Eugene Kirpichov
http://www.linkedin.com/in/eugenekirpichov

_______________________________________________
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help : https://help.launchpad.net/ListHelp