7:23 a.m.
Hi,
I am trying to configure RHEL 6.3 via cloud-init.
I am using cloud-init-0.6.3-0.7.bzr532.el6.noarch package and have a RHEL 6.3
guest os.
iso format ant label are:
[root@vm-17-184 cloudinit]# blkid /dev/sr0
/dev/sr0: LABEL="cidata" TYPE="iso9660"
iso file content:
[root@vm-17-184 cdrom]# cat meta-data
instance-id: iid-abcdefg
network-interfaces: |
iface eth0 inet static
address 192.168.1.10
network 192.168.1.0
netmask 255.255.255.0
broadcast 192.168.1.255
gateway 192.168.1.254
and I try the user-data file:
[root@vm-17-184 ~]# cat cdrom/user-data
hostname: mynode
fqdn: mynode.example.com
manage_etc_hosts: true
There is no effect on the IP address or host name, am I doing something wrong?
Attached the cloud-init.log
Thank you,
Shahar Havivi.
8:21 a.m.
Update:
I manage to change the host name when I generate the iso via:
$ genisoimage -output seed.iso -volid cidata -joliet -rock user-data meta-data
On 09.12.12 15:23, Shahar Havivi wrote:
Hi,
I am trying to configure RHEL 6.3 via cloud-init.
I am using cloud-init-0.6.3-0.7.bzr532.el6.noarch package and have a RHEL 6.3
guest os.
iso format ant label are:
[root@vm-17-184 cloudinit]# blkid /dev/sr0
/dev/sr0: LABEL="cidata" TYPE="iso9660"
iso file content:
[root@vm-17-184 cdrom]# cat meta-data
instance-id: iid-abcdefg
network-interfaces: |
iface eth0 inet static
address 192.168.1.10
network 192.168.1.0
netmask 255.255.255.0
broadcast 192.168.1.255
gateway 192.168.1.254
and I try the user-data file:
[root@vm-17-184 ~]# cat cdrom/user-data
hostname: mynode
fqdn: mynode.example.com
manage_etc_hosts: true
There is no effect on the IP address or host name, am I doing something wrong?
Attached the cloud-init.log
Thank you,
Shahar Havivi.
Dec 6 06:07:18 vm-17-184 [CLOUDINIT] cloud-init[INFO]: cloud-init
start-local running: Thu, 06 Dec 2012 04:07:18 +0000. up 13.90 seconds
Dec 6 06:07:19 vm-17-184 [CLOUDINIT] __init__.py[DEBUG]: searching for data source in
['DataSourceNoCloud', 'DataSourceConfigDrive', 'DataSourceOVF']
Dec 6 06:07:19 vm-17-184 [CLOUDINIT] __init__.py[DEBUG]: Did not find data source.
searched classes: ['DataSourceNoCloud', 'DataSourceConfigDrive',
'DataSourceOVF']
Dec 6 06:07:19 vm-17-184 [CLOUDINIT] cloud-init[INFO]: cloud-init start running: Thu, 06
Dec 2012 04:07:19 +0000. up 14.63 seconds
Dec 6 06:07:19 vm-17-184 [CLOUDINIT] __init__.py[DEBUG]: searching for data source in
['DataSourceNoCloudNet', 'DataSourceConfigDriveNet',
'DataSourceOVFNet', 'DataSourceEc2']
Dec 6 06:07:19 vm-17-184 [CLOUDINIT] DataSourceEc2.py[DEBUG]: removed the following from
metadata urls: ['http://instance-data:8773']
Dec 6 06:08:09 vm-17-184 [CLOUDINIT] DataSourceEc2.py[WARNING]:
'http://169.254.169.254/2009-04-04/meta-data/instance-id' failed [50/120s]: url
error [timed out]
Dec 6 06:09:00 vm-17-184 [CLOUDINIT] DataSourceEc2.py[WARNING]:
'http://169.254.169.254/2009-04-04/meta-data/instance-id' failed [101/120s]: url
error [timed out]
Dec 6 06:09:18 vm-17-184 [CLOUDINIT] DataSourceEc2.py[WARNING]:
'http://169.254.169.254/2009-04-04/meta-data/instance-id' failed [119/120s]: url
error [timed out]
Dec 6 06:09:19 vm-17-184 [CLOUDINIT] DataSourceEc2.py[CRITICAL]: giving up on md after
120 seconds
Dec 6 06:09:19 vm-17-184 [CLOUDINIT] __init__.py[DEBUG]: Did not find data source.
searched classes: ['DataSourceNoCloudNet', 'DataSourceConfigDriveNet',
'DataSourceOVFNet', 'DataSourceEc2']
Dec 9 01:17:32 vm-17-184 [CLOUDINIT] cloud-init[INFO]: cloud-init start-local running:
Sat, 08 Dec 2012 23:17:32 +0000. up 13.67 seconds
Dec 9 01:17:32 vm-17-184 [CLOUDINIT] __init__.py[DEBUG]: searching for data source in
['DataSourceNoCloud', 'DataSourceConfigDrive', 'DataSourceOVF']
Dec 9 01:17:32 vm-17-184 [CLOUDINIT] __init__.py[DEBUG]: Did not find data source.
searched classes: ['DataSourceNoCloud', 'DataSourceConfigDrive',
'DataSourceOVF']
Dec 9 01:17:33 vm-17-184 [CLOUDINIT] cloud-init[INFO]: cloud-init start running: Sat, 08
Dec 2012 23:17:33 +0000. up 14.12 seconds
Dec 9 01:17:33 vm-17-184 [CLOUDINIT] __init__.py[DEBUG]: searching for data source in
['DataSourceNoCloudNet', 'DataSourceConfigDriveNet',
'DataSourceOVFNet', 'DataSourceEc2']
Dec 9 01:17:35 vm-17-184 [CLOUDINIT] DataSourceEc2.py[DEBUG]: removed the following from
metadata urls: ['http://instance-data:8773']
Dec 9 01:18:25 vm-17-184 [CLOUDINIT] DataSourceEc2.py[WARNING]:
'http://169.254.169.254/2009-04-04/meta-data/instance-id' failed [50/120s]: url
error [timed out]
Dec 9 01:19:16 vm-17-184 [CLOUDINIT] DataSourceEc2.py[WARNING]:
'http://169.254.169.254/2009-04-04/meta-data/instance-id' failed [101/120s]: url
error [timed out]
Dec 9 01:19:34 vm-17-184 [CLOUDINIT] DataSourceEc2.py[WARNING]:
'http://169.254.169.254/2009-04-04/meta-data/instance-id' failed [119/120s]: url
error [timed out]
Dec 9 01:19:35 vm-17-184 [CLOUDINIT] DataSourceEc2.py[CRITICAL]: giving up on md after
120 seconds
Dec 9 01:19:35 vm-17-184 [CLOUDINIT] __init__.py[DEBUG]: Did not find data source.
searched classes: ['DataSourceNoCloudNet', 'DataSourceConfigDriveNet',
'DataSourceOVFNet', 'DataSourceEc2']
Dec 9 01:53:25 vm-17-184 [CLOUDINIT] cloud-init[INFO]: cloud-init start-local running:
Sat, 08 Dec 2012 23:53:25 +0000. up 14.37 seconds
Dec 9 01:53:25 vm-17-184 [CLOUDINIT] __init__.py[DEBUG]: searching for data source in
['DataSourceNoCloud', 'DataSourceConfigDrive', 'DataSourceOVF']
Dec 9 01:53:25 vm-17-184 [CLOUDINIT] __init__.py[DEBUG]: Did not find data source.
searched classes: ['DataSourceNoCloud', 'DataSourceConfigDrive',
'DataSourceOVF']
Dec 9 01:53:25 vm-17-184 [CLOUDINIT] cloud-init[INFO]: cloud-init start running: Sat, 08
Dec 2012 23:53:25 +0000. up 14.83 seconds
Dec 9 01:53:25 vm-17-184 [CLOUDINIT] __init__.py[DEBUG]: searching for data source in
['DataSourceNoCloudNet', 'DataSourceConfigDriveNet',
'DataSourceOVFNet', 'DataSourceEc2']
Dec 9 01:53:27 vm-17-184 [CLOUDINIT] DataSourceEc2.py[DEBUG]: removed the following from
metadata urls: ['http://instance-data:8773']
Dec 9 01:54:18 vm-17-184 [CLOUDINIT] DataSourceEc2.py[WARNING]:
'http://169.254.169.254/2009-04-04/meta-data/instance-id' failed [50/120s]: url
error [timed out]
Dec 9 01:55:09 vm-17-184 [CLOUDINIT] DataSourceEc2.py[WARNING]:
'http://169.254.169.254/2009-04-04/meta-data/instance-id' failed [101/120s]: url
error [timed out]
Dec 9 01:55:27 vm-17-184 [CLOUDINIT] DataSourceEc2.py[WARNING]:
'http://169.254.169.254/2009-04-04/meta-data/instance-id' failed [119/120s]: url
error [timed out]
Dec 9 01:55:28 vm-17-184 [CLOUDINIT] DataSourceEc2.py[CRITICAL]: giving up on md after
120 seconds
Dec 9 01:55:28 vm-17-184 [CLOUDINIT] __init__.py[DEBUG]: Did not find data source.
searched classes: ['DataSourceNoCloudNet', 'DataSourceConfigDriveNet',
'DataSourceOVFNet', 'DataSourceEc2']
Dec 9 02:13:35 vm-17-184 [CLOUDINIT] cloud-init[INFO]: cloud-init start-local running:
Sun, 09 Dec 2012 00:13:35 +0000. up 11.82 seconds
Dec 9 02:13:35 vm-17-184 [CLOUDINIT] __init__.py[DEBUG]: searching for data source in
['DataSourceNoCloud', 'DataSourceConfigDrive', 'DataSourceOVF']
Dec 9 02:13:36 vm-17-184 [CLOUDINIT] __init__.py[DEBUG]: Did not find data source.
searched classes: ['DataSourceNoCloud', 'DataSourceConfigDrive',
'DataSourceOVF']
Dec 9 02:13:36 vm-17-184 [CLOUDINIT] cloud-init[INFO]: cloud-init start running: Sun, 09
Dec 2012 00:13:36 +0000. up 12.31 seconds
Dec 9 02:13:36 vm-17-184 [CLOUDINIT] __init__.py[DEBUG]: searching for data source in
['DataSourceNoCloudNet', 'DataSourceConfigDriveNet',
'DataSourceOVFNet', 'DataSourceEc2']
Dec 9 02:13:36 vm-17-184 [CLOUDINIT] DataSourceEc2.py[DEBUG]: removed the following from
metadata urls: ['http://instance-data:8773']
Dec 9 02:14:26 vm-17-184 [CLOUDINIT] DataSourceEc2.py[WARNING]:
'http://169.254.169.254/2009-04-04/meta-data/instance-id' failed [50/120s]: url
error [timed out]
Dec 9 02:15:17 vm-17-184 [CLOUDINIT] DataSourceEc2.py[WARNING]:
'http://169.254.169.254/2009-04-04/meta-data/instance-id' failed [101/120s]: url
error [timed out]
Dec 9 02:15:35 vm-17-184 [CLOUDINIT] DataSourceEc2.py[WARNING]:
'http://169.254.169.254/2009-04-04/meta-data/instance-id' failed [119/120s]: url
error [timed out]
Dec 9 02:15:36 vm-17-184 [CLOUDINIT] DataSourceEc2.py[CRITICAL]: giving up on md after
120 seconds
Dec 9 02:15:36 vm-17-184 [CLOUDINIT] __init__.py[DEBUG]: Did not find data source.
searched classes: ['DataSourceNoCloudNet', 'DataSourceConfigDriveNet',
'DataSourceOVFNet', 'DataSourceEc2']
5:31 a.m.
Hi,
I had a little progress but still I have a questions.
I can set the hostname but not the ip:
meta-data:
instance-id: iid-test4
local-hostname: test4
local-ipv4: 192.168.1.1
the ip field is ignored...
what interface does the ip suppose to set if I have a few?
On 09.12.12 16:21, Shahar Havivi wrote:
Update:
I manage to change the host name when I generate the iso via:
$ genisoimage -output seed.iso -volid cidata -joliet -rock user-data meta-data
On 09.12.12 15:23, Shahar Havivi wrote:
> Hi,
> I am trying to configure RHEL 6.3 via cloud-init.
> I am using cloud-init-0.6.3-0.7.bzr532.el6.noarch package and have a RHEL 6.3
> guest os.
>
> iso format ant label are:
> [root@vm-17-184 cloudinit]# blkid /dev/sr0
> /dev/sr0: LABEL="cidata" TYPE="iso9660"
>
> iso file content:
> [root@vm-17-184 cdrom]# cat meta-data
> instance-id: iid-abcdefg
> network-interfaces: |
> iface eth0 inet static
> address 192.168.1.10
> network 192.168.1.0
> netmask 255.255.255.0
> broadcast 192.168.1.255
> gateway 192.168.1.254
>
> and I try the user-data file:
> [root@vm-17-184 ~]# cat cdrom/user-data
> hostname: mynode
> fqdn: mynode.example.com
> manage_etc_hosts: true
>
>
> There is no effect on the IP address or host name, am I doing something wrong?
>
> Attached the cloud-init.log
> Thank you,
> Shahar Havivi.
> Dec 6 06:07:18 vm-17-184 [CLOUDINIT] cloud-init[INFO]: cloud-init start-local
running: Thu, 06 Dec 2012 04:07:18 +0000. up 13.90 seconds
> Dec 6 06:07:19 vm-17-184 [CLOUDINIT] __init__.py[DEBUG]: searching for data source
in ['DataSourceNoCloud', 'DataSourceConfigDrive',
'DataSourceOVF']
> Dec 6 06:07:19 vm-17-184 [CLOUDINIT] __init__.py[DEBUG]: Did not find data source.
searched classes: ['DataSourceNoCloud', 'DataSourceConfigDrive',
'DataSourceOVF']
> Dec 6 06:07:19 vm-17-184 [CLOUDINIT] cloud-init[INFO]: cloud-init start running:
Thu, 06 Dec 2012 04:07:19 +0000. up 14.63 seconds
> Dec 6 06:07:19 vm-17-184 [CLOUDINIT] __init__.py[DEBUG]: searching for data source
in ['DataSourceNoCloudNet', 'DataSourceConfigDriveNet',
'DataSourceOVFNet', 'DataSourceEc2']
> Dec 6 06:07:19 vm-17-184 [CLOUDINIT] DataSourceEc2.py[DEBUG]: removed the following
from metadata urls: ['http://instance-data:8773']
> Dec 6 06:08:09 vm-17-184 [CLOUDINIT] DataSourceEc2.py[WARNING]:
'http://169.254.169.254/2009-04-04/meta-data/instance-id' failed [50/120s]: url
error [timed out]
> Dec 6 06:09:00 vm-17-184 [CLOUDINIT] DataSourceEc2.py[WARNING]:
'http://169.254.169.254/2009-04-04/meta-data/instance-id' failed [101/120s]: url
error [timed out]
> Dec 6 06:09:18 vm-17-184 [CLOUDINIT] DataSourceEc2.py[WARNING]:
'http://169.254.169.254/2009-04-04/meta-data/instance-id' failed [119/120s]: url
error [timed out]
> Dec 6 06:09:19 vm-17-184 [CLOUDINIT] DataSourceEc2.py[CRITICAL]: giving up on md
after 120 seconds
> Dec 6 06:09:19 vm-17-184 [CLOUDINIT] __init__.py[DEBUG]: Did not find data source.
searched classes: ['DataSourceNoCloudNet', 'DataSourceConfigDriveNet',
'DataSourceOVFNet', 'DataSourceEc2']
> Dec 9 01:17:32 vm-17-184 [CLOUDINIT] cloud-init[INFO]: cloud-init start-local
running: Sat, 08 Dec 2012 23:17:32 +0000. up 13.67 seconds
> Dec 9 01:17:32 vm-17-184 [CLOUDINIT] __init__.py[DEBUG]: searching for data source
in ['DataSourceNoCloud', 'DataSourceConfigDrive',
'DataSourceOVF']
> Dec 9 01:17:32 vm-17-184 [CLOUDINIT] __init__.py[DEBUG]: Did not find data source.
searched classes: ['DataSourceNoCloud', 'DataSourceConfigDrive',
'DataSourceOVF']
> Dec 9 01:17:33 vm-17-184 [CLOUDINIT] cloud-init[INFO]: cloud-init start running:
Sat, 08 Dec 2012 23:17:33 +0000. up 14.12 seconds
> Dec 9 01:17:33 vm-17-184 [CLOUDINIT] __init__.py[DEBUG]: searching for data source
in ['DataSourceNoCloudNet', 'DataSourceConfigDriveNet',
'DataSourceOVFNet', 'DataSourceEc2']
> Dec 9 01:17:35 vm-17-184 [CLOUDINIT] DataSourceEc2.py[DEBUG]: removed the following
from metadata urls: ['http://instance-data:8773']
> Dec 9 01:18:25 vm-17-184 [CLOUDINIT] DataSourceEc2.py[WARNING]:
'http://169.254.169.254/2009-04-04/meta-data/instance-id' failed [50/120s]: url
error [timed out]
> Dec 9 01:19:16 vm-17-184 [CLOUDINIT] DataSourceEc2.py[WARNING]:
'http://169.254.169.254/2009-04-04/meta-data/instance-id' failed [101/120s]: url
error [timed out]
> Dec 9 01:19:34 vm-17-184 [CLOUDINIT] DataSourceEc2.py[WARNING]:
'http://169.254.169.254/2009-04-04/meta-data/instance-id' failed [119/120s]: url
error [timed out]
> Dec 9 01:19:35 vm-17-184 [CLOUDINIT] DataSourceEc2.py[CRITICAL]: giving up on md
after 120 seconds
> Dec 9 01:19:35 vm-17-184 [CLOUDINIT] __init__.py[DEBUG]: Did not find data source.
searched classes: ['DataSourceNoCloudNet', 'DataSourceConfigDriveNet',
'DataSourceOVFNet', 'DataSourceEc2']
> Dec 9 01:53:25 vm-17-184 [CLOUDINIT] cloud-init[INFO]: cloud-init start-local
running: Sat, 08 Dec 2012 23:53:25 +0000. up 14.37 seconds
> Dec 9 01:53:25 vm-17-184 [CLOUDINIT] __init__.py[DEBUG]: searching for data source
in ['DataSourceNoCloud', 'DataSourceConfigDrive',
'DataSourceOVF']
> Dec 9 01:53:25 vm-17-184 [CLOUDINIT] __init__.py[DEBUG]: Did not find data source.
searched classes: ['DataSourceNoCloud', 'DataSourceConfigDrive',
'DataSourceOVF']
> Dec 9 01:53:25 vm-17-184 [CLOUDINIT] cloud-init[INFO]: cloud-init start running:
Sat, 08 Dec 2012 23:53:25 +0000. up 14.83 seconds
> Dec 9 01:53:25 vm-17-184 [CLOUDINIT] __init__.py[DEBUG]: searching for data source
in ['DataSourceNoCloudNet', 'DataSourceConfigDriveNet',
'DataSourceOVFNet', 'DataSourceEc2']
> Dec 9 01:53:27 vm-17-184 [CLOUDINIT] DataSourceEc2.py[DEBUG]: removed the following
from metadata urls: ['http://instance-data:8773']
> Dec 9 01:54:18 vm-17-184 [CLOUDINIT] DataSourceEc2.py[WARNING]:
'http://169.254.169.254/2009-04-04/meta-data/instance-id' failed [50/120s]: url
error [timed out]
> Dec 9 01:55:09 vm-17-184 [CLOUDINIT] DataSourceEc2.py[WARNING]:
'http://169.254.169.254/2009-04-04/meta-data/instance-id' failed [101/120s]: url
error [timed out]
> Dec 9 01:55:27 vm-17-184 [CLOUDINIT] DataSourceEc2.py[WARNING]:
'http://169.254.169.254/2009-04-04/meta-data/instance-id' failed [119/120s]: url
error [timed out]
> Dec 9 01:55:28 vm-17-184 [CLOUDINIT] DataSourceEc2.py[CRITICAL]: giving up on md
after 120 seconds
> Dec 9 01:55:28 vm-17-184 [CLOUDINIT] __init__.py[DEBUG]: Did not find data source.
searched classes: ['DataSourceNoCloudNet', 'DataSourceConfigDriveNet',
'DataSourceOVFNet', 'DataSourceEc2']
> Dec 9 02:13:35 vm-17-184 [CLOUDINIT] cloud-init[INFO]: cloud-init start-local
running: Sun, 09 Dec 2012 00:13:35 +0000. up 11.82 seconds
> Dec 9 02:13:35 vm-17-184 [CLOUDINIT] __init__.py[DEBUG]: searching for data source
in ['DataSourceNoCloud', 'DataSourceConfigDrive',
'DataSourceOVF']
> Dec 9 02:13:36 vm-17-184 [CLOUDINIT] __init__.py[DEBUG]: Did not find data source.
searched classes: ['DataSourceNoCloud', 'DataSourceConfigDrive',
'DataSourceOVF']
> Dec 9 02:13:36 vm-17-184 [CLOUDINIT] cloud-init[INFO]: cloud-init start running:
Sun, 09 Dec 2012 00:13:36 +0000. up 12.31 seconds
> Dec 9 02:13:36 vm-17-184 [CLOUDINIT] __init__.py[DEBUG]: searching for data source
in ['DataSourceNoCloudNet', 'DataSourceConfigDriveNet',
'DataSourceOVFNet', 'DataSourceEc2']
> Dec 9 02:13:36 vm-17-184 [CLOUDINIT] DataSourceEc2.py[DEBUG]: removed the following
from metadata urls: ['http://instance-data:8773']
> Dec 9 02:14:26 vm-17-184 [CLOUDINIT] DataSourceEc2.py[WARNING]:
'http://169.254.169.254/2009-04-04/meta-data/instance-id' failed [50/120s]: url
error [timed out]
> Dec 9 02:15:17 vm-17-184 [CLOUDINIT] DataSourceEc2.py[WARNING]:
'http://169.254.169.254/2009-04-04/meta-data/instance-id' failed [101/120s]: url
error [timed out]
> Dec 9 02:15:35 vm-17-184 [CLOUDINIT] DataSourceEc2.py[WARNING]:
'http://169.254.169.254/2009-04-04/meta-data/instance-id' failed [119/120s]: url
error [timed out]
> Dec 9 02:15:36 vm-17-184 [CLOUDINIT] DataSourceEc2.py[CRITICAL]: giving up on md
after 120 seconds
> Dec 9 02:15:36 vm-17-184 [CLOUDINIT] __init__.py[DEBUG]: Did not find data source.
searched classes: ['DataSourceNoCloudNet', 'DataSourceConfigDriveNet',
'DataSourceOVFNet', 'DataSourceEc2']
8:11 a.m.
Shahar,
Are you launching on EC2 or a different cloud backend?
If EC2, I am not sure, but I don't think you can set an VM's IP address
on EC2. So you might be encountering an EC2 issue.
It looks as if you are not using user-data alone but the yaml formated
meta-data, which user-data can be a part of, in a iso or vfat filesystem
with a known label.
The log below may be from one of your earlier runs, before you
started using genisoimage to pass in the meta-data. Does the lates
log file and shed any light on the IP address issue?
I'm not overly familiar with it but I know there is a utility in cloud-utils
called 'cloud-localds' [1] that creates a iso or vfat. the --help
output will
give example usage, and you can look at the created disk image.
If you are launching on Openstack it uses the data source:
"config-drive-v2",
which is an option for passing metadata to instances in OpenStack folsom
and later (doc added at [2])
[1]
http://bazaar.launchpad.net/~cloud-utils-dev/cloud-utils/trunk/view/head:...
[2] https://review.openstack.org/#/c/16504/
Hope this helps and let me know what the latest log file shows if you
need more help.
Joe
On 12/10/2012 06:31 AM, Shahar Havivi wrote:
Hi,
I had a little progress but still I have a questions.
I can set the hostname but not the ip:
meta-data:
instance-id: iid-test4
local-hostname: test4
local-ipv4: 192.168.1.1
the ip field is ignored...
what interface does the ip suppose to set if I have a few?
On 09.12.12 16:21, Shahar Havivi wrote:
> Update:
> I manage to change the host name when I generate the iso via:
> $ genisoimage -output seed.iso -volid cidata -joliet -rock user-data meta-data
>
> On 09.12.12 15:23, Shahar Havivi wrote:
>> Hi,
>> I am trying to configure RHEL 6.3 via cloud-init.
>> I am using cloud-init-0.6.3-0.7.bzr532.el6.noarch package and have a RHEL 6.3
>> guest os.
>>
>> iso format ant label are:
>> [root@vm-17-184 cloudinit]# blkid /dev/sr0
>> /dev/sr0: LABEL="cidata" TYPE="iso9660"
>>
>> iso file content:
>> [root@vm-17-184 cdrom]# cat meta-data
>> instance-id: iid-abcdefg
>> network-interfaces: |
>> iface eth0 inet static
>> address 192.168.1.10
>> network 192.168.1.0
>> netmask 255.255.255.0
>> broadcast 192.168.1.255
>> gateway 192.168.1.254
>>
>> and I try the user-data file:
>> [root@vm-17-184 ~]# cat cdrom/user-data
>> hostname: mynode
>> fqdn: mynode.example.com
>> manage_etc_hosts: true
>>
>>
>> There is no effect on the IP address or host name, am I doing something wrong?
>>
>> Attached the cloud-init.log
>> Thank you,
>> Shahar Havivi.
>> Dec 6 06:07:18 vm-17-184 [CLOUDINIT] cloud-init[INFO]: cloud-init start-local
running: Thu, 06 Dec 2012 04:07:18 +0000. up 13.90 seconds
>> Dec 6 06:07:19 vm-17-184 [CLOUDINIT] __init__.py[DEBUG]: searching for data
source in ['DataSourceNoCloud', 'DataSourceConfigDrive',
'DataSourceOVF']
>> Dec 6 06:07:19 vm-17-184 [CLOUDINIT] __init__.py[DEBUG]: Did not find data
source. searched classes: ['DataSourceNoCloud', 'DataSourceConfigDrive',
'DataSourceOVF']
>> Dec 6 06:07:19 vm-17-184 [CLOUDINIT] cloud-init[INFO]: cloud-init start running:
Thu, 06 Dec 2012 04:07:19 +0000. up 14.63 seconds
>> Dec 6 06:07:19 vm-17-184 [CLOUDINIT] __init__.py[DEBUG]: searching for data
source in ['DataSourceNoCloudNet', 'DataSourceConfigDriveNet',
'DataSourceOVFNet', 'DataSourceEc2']
>> Dec 6 06:07:19 vm-17-184 [CLOUDINIT] DataSourceEc2.py[DEBUG]: removed the
following from metadata urls: ['http://instance-data:8773']
>> Dec 6 06:08:09 vm-17-184 [CLOUDINIT] DataSourceEc2.py[WARNING]:
'http://169.254.169.254/2009-04-04/meta-data/instance-id' failed [50/120s]: url
error [timed out]
>> Dec 6 06:09:00 vm-17-184 [CLOUDINIT] DataSourceEc2.py[WARNING]:
'http://169.254.169.254/2009-04-04/meta-data/instance-id' failed [101/120s]: url
error [timed out]
>> Dec 6 06:09:18 vm-17-184 [CLOUDINIT] DataSourceEc2.py[WARNING]:
'http://169.254.169.254/2009-04-04/meta-data/instance-id' failed [119/120s]: url
error [timed out]
>> Dec 6 06:09:19 vm-17-184 [CLOUDINIT] DataSourceEc2.py[CRITICAL]: giving up on md
after 120 seconds
>> Dec 6 06:09:19 vm-17-184 [CLOUDINIT] __init__.py[DEBUG]: Did not find data
source. searched classes: ['DataSourceNoCloudNet',
'DataSourceConfigDriveNet', 'DataSourceOVFNet', 'DataSourceEc2']
>> Dec 9 01:17:32 vm-17-184 [CLOUDINIT] cloud-init[INFO]: cloud-init start-local
running: Sat, 08 Dec 2012 23:17:32 +0000. up 13.67 seconds
>> Dec 9 01:17:32 vm-17-184 [CLOUDINIT] __init__.py[DEBUG]: searching for data
source in ['DataSourceNoCloud', 'DataSourceConfigDrive',
'DataSourceOVF']
>> Dec 9 01:17:32 vm-17-184 [CLOUDINIT] __init__.py[DEBUG]: Did not find data
source. searched classes: ['DataSourceNoCloud', 'DataSourceConfigDrive',
'DataSourceOVF']
>> Dec 9 01:17:33 vm-17-184 [CLOUDINIT] cloud-init[INFO]: cloud-init start running:
Sat, 08 Dec 2012 23:17:33 +0000. up 14.12 seconds
>> Dec 9 01:17:33 vm-17-184 [CLOUDINIT] __init__.py[DEBUG]: searching for data
source in ['DataSourceNoCloudNet', 'DataSourceConfigDriveNet',
'DataSourceOVFNet', 'DataSourceEc2']
>> Dec 9 01:17:35 vm-17-184 [CLOUDINIT] DataSourceEc2.py[DEBUG]: removed the
following from metadata urls: ['http://instance-data:8773']
>> Dec 9 01:18:25 vm-17-184 [CLOUDINIT] DataSourceEc2.py[WARNING]:
'http://169.254.169.254/2009-04-04/meta-data/instance-id' failed [50/120s]: url
error [timed out]
>> Dec 9 01:19:16 vm-17-184 [CLOUDINIT] DataSourceEc2.py[WARNING]:
'http://169.254.169.254/2009-04-04/meta-data/instance-id' failed [101/120s]: url
error [timed out]
>> Dec 9 01:19:34 vm-17-184 [CLOUDINIT] DataSourceEc2.py[WARNING]:
'http://169.254.169.254/2009-04-04/meta-data/instance-id' failed [119/120s]: url
error [timed out]
>> Dec 9 01:19:35 vm-17-184 [CLOUDINIT] DataSourceEc2.py[CRITICAL]: giving up on md
after 120 seconds
>> Dec 9 01:19:35 vm-17-184 [CLOUDINIT] __init__.py[DEBUG]: Did not find data
source. searched classes: ['DataSourceNoCloudNet',
'DataSourceConfigDriveNet', 'DataSourceOVFNet', 'DataSourceEc2']
>> Dec 9 01:53:25 vm-17-184 [CLOUDINIT] cloud-init[INFO]: cloud-init start-local
running: Sat, 08 Dec 2012 23:53:25 +0000. up 14.37 seconds
>> Dec 9 01:53:25 vm-17-184 [CLOUDINIT] __init__.py[DEBUG]: searching for data
source in ['DataSourceNoCloud', 'DataSourceConfigDrive',
'DataSourceOVF']
>> Dec 9 01:53:25 vm-17-184 [CLOUDINIT] __init__.py[DEBUG]: Did not find data
source. searched classes: ['DataSourceNoCloud', 'DataSourceConfigDrive',
'DataSourceOVF']
>> Dec 9 01:53:25 vm-17-184 [CLOUDINIT] cloud-init[INFO]: cloud-init start running:
Sat, 08 Dec 2012 23:53:25 +0000. up 14.83 seconds
>> Dec 9 01:53:25 vm-17-184 [CLOUDINIT] __init__.py[DEBUG]: searching for data
source in ['DataSourceNoCloudNet', 'DataSourceConfigDriveNet',
'DataSourceOVFNet', 'DataSourceEc2']
>> Dec 9 01:53:27 vm-17-184 [CLOUDINIT] DataSourceEc2.py[DEBUG]: removed the
following from metadata urls: ['http://instance-data:8773']
>> Dec 9 01:54:18 vm-17-184 [CLOUDINIT] DataSourceEc2.py[WARNING]:
'http://169.254.169.254/2009-04-04/meta-data/instance-id' failed [50/120s]: url
error [timed out]
>> Dec 9 01:55:09 vm-17-184 [CLOUDINIT] DataSourceEc2.py[WARNING]:
'http://169.254.169.254/2009-04-04/meta-data/instance-id' failed [101/120s]: url
error [timed out]
>> Dec 9 01:55:27 vm-17-184 [CLOUDINIT] DataSourceEc2.py[WARNING]:
'http://169.254.169.254/2009-04-04/meta-data/instance-id' failed [119/120s]: url
error [timed out]
>> Dec 9 01:55:28 vm-17-184 [CLOUDINIT] DataSourceEc2.py[CRITICAL]: giving up on md
after 120 seconds
>> Dec 9 01:55:28 vm-17-184 [CLOUDINIT] __init__.py[DEBUG]: Did not find data
source. searched classes: ['DataSourceNoCloudNet',
'DataSourceConfigDriveNet', 'DataSourceOVFNet', 'DataSourceEc2']
>> Dec 9 02:13:35 vm-17-184 [CLOUDINIT] cloud-init[INFO]: cloud-init start-local
running: Sun, 09 Dec 2012 00:13:35 +0000. up 11.82 seconds
>> Dec 9 02:13:35 vm-17-184 [CLOUDINIT] __init__.py[DEBUG]: searching for data
source in ['DataSourceNoCloud', 'DataSourceConfigDrive',
'DataSourceOVF']
>> Dec 9 02:13:36 vm-17-184 [CLOUDINIT] __init__.py[DEBUG]: Did not find data
source. searched classes: ['DataSourceNoCloud', 'DataSourceConfigDrive',
'DataSourceOVF']
>> Dec 9 02:13:36 vm-17-184 [CLOUDINIT] cloud-init[INFO]: cloud-init start running:
Sun, 09 Dec 2012 00:13:36 +0000. up 12.31 seconds
>> Dec 9 02:13:36 vm-17-184 [CLOUDINIT] __init__.py[DEBUG]: searching for data
source in ['DataSourceNoCloudNet', 'DataSourceConfigDriveNet',
'DataSourceOVFNet', 'DataSourceEc2']
>> Dec 9 02:13:36 vm-17-184 [CLOUDINIT] DataSourceEc2.py[DEBUG]: removed the
following from metadata urls: ['http://instance-data:8773']
>> Dec 9 02:14:26 vm-17-184 [CLOUDINIT] DataSourceEc2.py[WARNING]:
'http://169.254.169.254/2009-04-04/meta-data/instance-id' failed [50/120s]: url
error [timed out]
>> Dec 9 02:15:17 vm-17-184 [CLOUDINIT] DataSourceEc2.py[WARNING]:
'http://169.254.169.254/2009-04-04/meta-data/instance-id' failed [101/120s]: url
error [timed out]
>> Dec 9 02:15:35 vm-17-184 [CLOUDINIT] DataSourceEc2.py[WARNING]:
'http://169.254.169.254/2009-04-04/meta-data/instance-id' failed [119/120s]: url
error [timed out]
>> Dec 9 02:15:36 vm-17-184 [CLOUDINIT] DataSourceEc2.py[CRITICAL]: giving up on md
after 120 seconds
>> Dec 9 02:15:36 vm-17-184 [CLOUDINIT] __init__.py[DEBUG]: Did not find data
source. searched classes: ['DataSourceNoCloudNet',
'DataSourceConfigDriveNet', 'DataSourceOVFNet', 'DataSourceEc2']
8:38 a.m.
On 10.12.12 09:11, jvlcek wrote:
Shahar,
Are you launching on EC2 or a different cloud backend?
No, I am testing on oVirt.
The log is different now, and there is some exception regarding
apply_credentials().
Attaching the new log, look at the last run where the lines starts with:
Dec 10 16:31:12 vm-17-184
Thank you,
Shahar.
If EC2, I am not sure, but I don't think you can set an VM's IP address
on EC2. So you might be encountering an EC2 issue.
It looks as if you are not using user-data alone but the yaml formated
meta-data, which user-data can be a part of, in a iso or vfat filesystem
with a known label.
The log below may be from one of your earlier runs, before you
started using genisoimage to pass in the meta-data. Does the lates
log file and shed any light on the IP address issue?
I'm not overly familiar with it but I know there is a utility in cloud-utils
called 'cloud-localds' [1] that creates a iso or vfat. the --help
output will
give example usage, and you can look at the created disk image.
If you are launching on Openstack it uses the data source:
"config-drive-v2",
which is an option for passing metadata to instances in OpenStack folsom
and later (doc added at [2])
[1]
http://bazaar.launchpad.net/~cloud-utils-dev/cloud-utils/trunk/view/head:...
[2] https://review.openstack.org/#/c/16504/
Hope this helps and let me know what the latest log file shows if you
need more help.
Joe
On 12/10/2012 06:31 AM, Shahar Havivi wrote:
> Hi,
> I had a little progress but still I have a questions.
> I can set the hostname but not the ip:
> meta-data:
> instance-id: iid-test4
> local-hostname: test4
> local-ipv4: 192.168.1.1
>
> the ip field is ignored...
> what interface does the ip suppose to set if I have a few?
>
>
> On 09.12.12 16:21, Shahar Havivi wrote:
>> Update:
>> I manage to change the host name when I generate the iso via:
>> $ genisoimage -output seed.iso -volid cidata -joliet -rock user-data meta-data
>>
>> On 09.12.12 15:23, Shahar Havivi wrote:
>>> Hi,
>>> I am trying to configure RHEL 6.3 via cloud-init.
>>> I am using cloud-init-0.6.3-0.7.bzr532.el6.noarch package and have a RHEL
6.3
>>> guest os.
>>>
>>> iso format ant label are:
>>> [root@vm-17-184 cloudinit]# blkid /dev/sr0
>>> /dev/sr0: LABEL="cidata" TYPE="iso9660"
>>>
>>> iso file content:
>>> [root@vm-17-184 cdrom]# cat meta-data
>>> instance-id: iid-abcdefg
>>> network-interfaces: |
>>> iface eth0 inet static
>>> address 192.168.1.10
>>> network 192.168.1.0
>>> netmask 255.255.255.0
>>> broadcast 192.168.1.255
>>> gateway 192.168.1.254
>>>
>>> and I try the user-data file:
>>> [root@vm-17-184 ~]# cat cdrom/user-data
>>> hostname: mynode
>>> fqdn: mynode.example.com
>>> manage_etc_hosts: true
>>>
>>>
>>> There is no effect on the IP address or host name, am I doing something
wrong?
>>>
>>> Attached the cloud-init.log
>>> Thank you,
>>> Shahar Havivi.
>>> Dec 6 06:07:18 vm-17-184 [CLOUDINIT] cloud-init[INFO]: cloud-init
start-local running: Thu, 06 Dec 2012 04:07:18 +0000. up 13.90 seconds
>>> Dec 6 06:07:19 vm-17-184 [CLOUDINIT] __init__.py[DEBUG]: searching for data
source in ['DataSourceNoCloud', 'DataSourceConfigDrive',
'DataSourceOVF']
>>> Dec 6 06:07:19 vm-17-184 [CLOUDINIT] __init__.py[DEBUG]: Did not find data
source. searched classes: ['DataSourceNoCloud', 'DataSourceConfigDrive',
'DataSourceOVF']
>>> Dec 6 06:07:19 vm-17-184 [CLOUDINIT] cloud-init[INFO]: cloud-init start
running: Thu, 06 Dec 2012 04:07:19 +0000. up 14.63 seconds
>>> Dec 6 06:07:19 vm-17-184 [CLOUDINIT] __init__.py[DEBUG]: searching for data
source in ['DataSourceNoCloudNet', 'DataSourceConfigDriveNet',
'DataSourceOVFNet', 'DataSourceEc2']
>>> Dec 6 06:07:19 vm-17-184 [CLOUDINIT] DataSourceEc2.py[DEBUG]: removed the
following from metadata urls: ['http://instance-data:8773']
>>> Dec 6 06:08:09 vm-17-184 [CLOUDINIT] DataSourceEc2.py[WARNING]:
'http://169.254.169.254/2009-04-04/meta-data/instance-id' failed [50/120s]: url
error [timed out]
>>> Dec 6 06:09:00 vm-17-184 [CLOUDINIT] DataSourceEc2.py[WARNING]:
'http://169.254.169.254/2009-04-04/meta-data/instance-id' failed [101/120s]: url
error [timed out]
>>> Dec 6 06:09:18 vm-17-184 [CLOUDINIT] DataSourceEc2.py[WARNING]:
'http://169.254.169.254/2009-04-04/meta-data/instance-id' failed [119/120s]: url
error [timed out]
>>> Dec 6 06:09:19 vm-17-184 [CLOUDINIT] DataSourceEc2.py[CRITICAL]: giving up
on md after 120 seconds
>>> Dec 6 06:09:19 vm-17-184 [CLOUDINIT] __init__.py[DEBUG]: Did not find data
source. searched classes: ['DataSourceNoCloudNet',
'DataSourceConfigDriveNet', 'DataSourceOVFNet', 'DataSourceEc2']
>>> Dec 9 01:17:32 vm-17-184 [CLOUDINIT] cloud-init[INFO]: cloud-init
start-local running: Sat, 08 Dec 2012 23:17:32 +0000. up 13.67 seconds
>>> Dec 9 01:17:32 vm-17-184 [CLOUDINIT] __init__.py[DEBUG]: searching for data
source in ['DataSourceNoCloud', 'DataSourceConfigDrive',
'DataSourceOVF']
>>> Dec 9 01:17:32 vm-17-184 [CLOUDINIT] __init__.py[DEBUG]: Did not find data
source. searched classes: ['DataSourceNoCloud', 'DataSourceConfigDrive',
'DataSourceOVF']
>>> Dec 9 01:17:33 vm-17-184 [CLOUDINIT] cloud-init[INFO]: cloud-init start
running: Sat, 08 Dec 2012 23:17:33 +0000. up 14.12 seconds
>>> Dec 9 01:17:33 vm-17-184 [CLOUDINIT] __init__.py[DEBUG]: searching for data
source in ['DataSourceNoCloudNet', 'DataSourceConfigDriveNet',
'DataSourceOVFNet', 'DataSourceEc2']
>>> Dec 9 01:17:35 vm-17-184 [CLOUDINIT] DataSourceEc2.py[DEBUG]: removed the
following from metadata urls: ['http://instance-data:8773']
>>> Dec 9 01:18:25 vm-17-184 [CLOUDINIT] DataSourceEc2.py[WARNING]:
'http://169.254.169.254/2009-04-04/meta-data/instance-id' failed [50/120s]: url
error [timed out]
>>> Dec 9 01:19:16 vm-17-184 [CLOUDINIT] DataSourceEc2.py[WARNING]:
'http://169.254.169.254/2009-04-04/meta-data/instance-id' failed [101/120s]: url
error [timed out]
>>> Dec 9 01:19:34 vm-17-184 [CLOUDINIT] DataSourceEc2.py[WARNING]:
'http://169.254.169.254/2009-04-04/meta-data/instance-id' failed [119/120s]: url
error [timed out]
>>> Dec 9 01:19:35 vm-17-184 [CLOUDINIT] DataSourceEc2.py[CRITICAL]: giving up
on md after 120 seconds
>>> Dec 9 01:19:35 vm-17-184 [CLOUDINIT] __init__.py[DEBUG]: Did not find data
source. searched classes: ['DataSourceNoCloudNet',
'DataSourceConfigDriveNet', 'DataSourceOVFNet', 'DataSourceEc2']
>>> Dec 9 01:53:25 vm-17-184 [CLOUDINIT] cloud-init[INFO]: cloud-init
start-local running: Sat, 08 Dec 2012 23:53:25 +0000. up 14.37 seconds
>>> Dec 9 01:53:25 vm-17-184 [CLOUDINIT] __init__.py[DEBUG]: searching for data
source in ['DataSourceNoCloud', 'DataSourceConfigDrive',
'DataSourceOVF']
>>> Dec 9 01:53:25 vm-17-184 [CLOUDINIT] __init__.py[DEBUG]: Did not find data
source. searched classes: ['DataSourceNoCloud', 'DataSourceConfigDrive',
'DataSourceOVF']
>>> Dec 9 01:53:25 vm-17-184 [CLOUDINIT] cloud-init[INFO]: cloud-init start
running: Sat, 08 Dec 2012 23:53:25 +0000. up 14.83 seconds
>>> Dec 9 01:53:25 vm-17-184 [CLOUDINIT] __init__.py[DEBUG]: searching for data
source in ['DataSourceNoCloudNet', 'DataSourceConfigDriveNet',
'DataSourceOVFNet', 'DataSourceEc2']
>>> Dec 9 01:53:27 vm-17-184 [CLOUDINIT] DataSourceEc2.py[DEBUG]: removed the
following from metadata urls: ['http://instance-data:8773']
>>> Dec 9 01:54:18 vm-17-184 [CLOUDINIT] DataSourceEc2.py[WARNING]:
'http://169.254.169.254/2009-04-04/meta-data/instance-id' failed [50/120s]: url
error [timed out]
>>> Dec 9 01:55:09 vm-17-184 [CLOUDINIT] DataSourceEc2.py[WARNING]:
'http://169.254.169.254/2009-04-04/meta-data/instance-id' failed [101/120s]: url
error [timed out]
>>> Dec 9 01:55:27 vm-17-184 [CLOUDINIT] DataSourceEc2.py[WARNING]:
'http://169.254.169.254/2009-04-04/meta-data/instance-id' failed [119/120s]: url
error [timed out]
>>> Dec 9 01:55:28 vm-17-184 [CLOUDINIT] DataSourceEc2.py[CRITICAL]: giving up
on md after 120 seconds
>>> Dec 9 01:55:28 vm-17-184 [CLOUDINIT] __init__.py[DEBUG]: Did not find data
source. searched classes: ['DataSourceNoCloudNet',
'DataSourceConfigDriveNet', 'DataSourceOVFNet', 'DataSourceEc2']
>>> Dec 9 02:13:35 vm-17-184 [CLOUDINIT] cloud-init[INFO]: cloud-init
start-local running: Sun, 09 Dec 2012 00:13:35 +0000. up 11.82 seconds
>>> Dec 9 02:13:35 vm-17-184 [CLOUDINIT] __init__.py[DEBUG]: searching for data
source in ['DataSourceNoCloud', 'DataSourceConfigDrive',
'DataSourceOVF']
>>> Dec 9 02:13:36 vm-17-184 [CLOUDINIT] __init__.py[DEBUG]: Did not find data
source. searched classes: ['DataSourceNoCloud', 'DataSourceConfigDrive',
'DataSourceOVF']
>>> Dec 9 02:13:36 vm-17-184 [CLOUDINIT] cloud-init[INFO]: cloud-init start
running: Sun, 09 Dec 2012 00:13:36 +0000. up 12.31 seconds
>>> Dec 9 02:13:36 vm-17-184 [CLOUDINIT] __init__.py[DEBUG]: searching for data
source in ['DataSourceNoCloudNet', 'DataSourceConfigDriveNet',
'DataSourceOVFNet', 'DataSourceEc2']
>>> Dec 9 02:13:36 vm-17-184 [CLOUDINIT] DataSourceEc2.py[DEBUG]: removed the
following from metadata urls: ['http://instance-data:8773']
>>> Dec 9 02:14:26 vm-17-184 [CLOUDINIT] DataSourceEc2.py[WARNING]:
'http://169.254.169.254/2009-04-04/meta-data/instance-id' failed [50/120s]: url
error [timed out]
>>> Dec 9 02:15:17 vm-17-184 [CLOUDINIT] DataSourceEc2.py[WARNING]:
'http://169.254.169.254/2009-04-04/meta-data/instance-id' failed [101/120s]: url
error [timed out]
>>> Dec 9 02:15:35 vm-17-184 [CLOUDINIT] DataSourceEc2.py[WARNING]:
'http://169.254.169.254/2009-04-04/meta-data/instance-id' failed [119/120s]: url
error [timed out]
>>> Dec 9 02:15:36 vm-17-184 [CLOUDINIT] DataSourceEc2.py[CRITICAL]: giving up
on md after 120 seconds
>>> Dec 9 02:15:36 vm-17-184 [CLOUDINIT] __init__.py[DEBUG]: Did not find data
source. searched classes: ['DataSourceNoCloudNet',
'DataSourceConfigDriveNet', 'DataSourceOVFNet', 'DataSourceEc2']
9:55 a.m.
Shahar,
It's complaining about the ec2-user not being there?
Are you specifying the ec2-user in the cloud-init.conf file or are you just
using root?
The version of cloud-init you are using is also a bit old. The user
creation/
default user handling has changed. We are targeting cloud-init-0.7.1-2 for
RHEL6.4
Joe
On 12/10/2012 09:38 AM, Shahar Havivi wrote:
On 10.12.12 09:11, jvlcek wrote:
> Shahar,
>
> Are you launching on EC2 or a different cloud backend?
No, I am testing on oVirt.
The log is different now, and there is some exception regarding
apply_credentials().
Attaching the new log, look at the last run where the lines starts with:
Dec 10 16:31:12 vm-17-184
Thank you,
Shahar.
> If EC2, I am not sure, but I don't think you can set an VM's IP address
> on EC2. So you might be encountering an EC2 issue.
>
> It looks as if you are not using user-data alone but the yaml formated
> meta-data, which user-data can be a part of, in a iso or vfat filesystem
> with a known label.
>
> The log below may be from one of your earlier runs, before you
> started using genisoimage to pass in the meta-data. Does the lates
> log file and shed any light on the IP address issue?
>
> I'm not overly familiar with it but I know there is a utility in cloud-utils
> called 'cloud-localds' [1] that creates a iso or vfat. the --help
> output will
> give example usage, and you can look at the created disk image.
>
> If you are launching on Openstack it uses the data source:
> "config-drive-v2",
> which is an option for passing metadata to instances in OpenStack folsom
> and later (doc added at [2])
>
> [1]
>
http://bazaar.launchpad.net/~cloud-utils-dev/cloud-utils/trunk/view/head:...
>
> [2] https://review.openstack.org/#/c/16504/
>
>
> Hope this helps and let me know what the latest log file shows if you
> need more help.
>
> Joe
>
> On 12/10/2012 06:31 AM, Shahar Havivi wrote:
>> Hi,
>> I had a little progress but still I have a questions.
>> I can set the hostname but not the ip:
>> meta-data:
>> instance-id: iid-test4
>> local-hostname: test4
>> local-ipv4: 192.168.1.1
>>
>> the ip field is ignored...
>> what interface does the ip suppose to set if I have a few?
>>
>>
>> On 09.12.12 16:21, Shahar Havivi wrote:
>>> Update:
>>> I manage to change the host name when I generate the iso via:
>>> $ genisoimage -output seed.iso -volid cidata -joliet -rock user-data
meta-data
>>>
>>> On 09.12.12 15:23, Shahar Havivi wrote:
>>>> Hi,
>>>> I am trying to configure RHEL 6.3 via cloud-init.
>>>> I am using cloud-init-0.6.3-0.7.bzr532.el6.noarch package and have a RHEL
6.3
>>>> guest os.
>>>>
>>>> iso format ant label are:
>>>> [root@vm-17-184 cloudinit]# blkid /dev/sr0
>>>> /dev/sr0: LABEL="cidata" TYPE="iso9660"
>>>>
>>>> iso file content:
>>>> [root@vm-17-184 cdrom]# cat meta-data
>>>> instance-id: iid-abcdefg
>>>> network-interfaces: |
>>>> iface eth0 inet static
>>>> address 192.168.1.10
>>>> network 192.168.1.0
>>>> netmask 255.255.255.0
>>>> broadcast 192.168.1.255
>>>> gateway 192.168.1.254
>>>>
>>>> and I try the user-data file:
>>>> [root@vm-17-184 ~]# cat cdrom/user-data
>>>> hostname: mynode
>>>> fqdn: mynode.example.com
>>>> manage_etc_hosts: true
>>>>
>>>>
>>>> There is no effect on the IP address or host name, am I doing something
wrong?
>>>>
>>>> Attached the cloud-init.log
>>>> Thank you,
>>>> Shahar Havivi.
>>>> Dec 6 06:07:18 vm-17-184 [CLOUDINIT] cloud-init[INFO]: cloud-init
start-local running: Thu, 06 Dec 2012 04:07:18 +0000. up 13.90 seconds
>>>> Dec 6 06:07:19 vm-17-184 [CLOUDINIT] __init__.py[DEBUG]: searching for
data source in ['DataSourceNoCloud', 'DataSourceConfigDrive',
'DataSourceOVF']
>>>> Dec 6 06:07:19 vm-17-184 [CLOUDINIT] __init__.py[DEBUG]: Did not find
data source. searched classes: ['DataSourceNoCloud',
'DataSourceConfigDrive', 'DataSourceOVF']
>>>> Dec 6 06:07:19 vm-17-184 [CLOUDINIT] cloud-init[INFO]: cloud-init start
running: Thu, 06 Dec 2012 04:07:19 +0000. up 14.63 seconds
>>>> Dec 6 06:07:19 vm-17-184 [CLOUDINIT] __init__.py[DEBUG]: searching for
data source in ['DataSourceNoCloudNet', 'DataSourceConfigDriveNet',
'DataSourceOVFNet', 'DataSourceEc2']
>>>> Dec 6 06:07:19 vm-17-184 [CLOUDINIT] DataSourceEc2.py[DEBUG]: removed
the following from metadata urls: ['http://instance-data:8773']
>>>> Dec 6 06:08:09 vm-17-184 [CLOUDINIT] DataSourceEc2.py[WARNING]:
'http://169.254.169.254/2009-04-04/meta-data/instance-id' failed [50/120s]: url
error [timed out]
>>>> Dec 6 06:09:00 vm-17-184 [CLOUDINIT] DataSourceEc2.py[WARNING]:
'http://169.254.169.254/2009-04-04/meta-data/instance-id' failed [101/120s]: url
error [timed out]
>>>> Dec 6 06:09:18 vm-17-184 [CLOUDINIT] DataSourceEc2.py[WARNING]:
'http://169.254.169.254/2009-04-04/meta-data/instance-id' failed [119/120s]: url
error [timed out]
>>>> Dec 6 06:09:19 vm-17-184 [CLOUDINIT] DataSourceEc2.py[CRITICAL]: giving
up on md after 120 seconds
>>>> Dec 6 06:09:19 vm-17-184 [CLOUDINIT] __init__.py[DEBUG]: Did not find
data source. searched classes: ['DataSourceNoCloudNet',
'DataSourceConfigDriveNet', 'DataSourceOVFNet', 'DataSourceEc2']
>>>> Dec 9 01:17:32 vm-17-184 [CLOUDINIT] cloud-init[INFO]: cloud-init
start-local running: Sat, 08 Dec 2012 23:17:32 +0000. up 13.67 seconds
>>>> Dec 9 01:17:32 vm-17-184 [CLOUDINIT] __init__.py[DEBUG]: searching for
data source in ['DataSourceNoCloud', 'DataSourceConfigDrive',
'DataSourceOVF']
>>>> Dec 9 01:17:32 vm-17-184 [CLOUDINIT] __init__.py[DEBUG]: Did not find
data source. searched classes: ['DataSourceNoCloud',
'DataSourceConfigDrive', 'DataSourceOVF']
>>>> Dec 9 01:17:33 vm-17-184 [CLOUDINIT] cloud-init[INFO]: cloud-init start
running: Sat, 08 Dec 2012 23:17:33 +0000. up 14.12 seconds
>>>> Dec 9 01:17:33 vm-17-184 [CLOUDINIT] __init__.py[DEBUG]: searching for
data source in ['DataSourceNoCloudNet', 'DataSourceConfigDriveNet',
'DataSourceOVFNet', 'DataSourceEc2']
>>>> Dec 9 01:17:35 vm-17-184 [CLOUDINIT] DataSourceEc2.py[DEBUG]: removed
the following from metadata urls: ['http://instance-data:8773']
>>>> Dec 9 01:18:25 vm-17-184 [CLOUDINIT] DataSourceEc2.py[WARNING]:
'http://169.254.169.254/2009-04-04/meta-data/instance-id' failed [50/120s]: url
error [timed out]
>>>> Dec 9 01:19:16 vm-17-184 [CLOUDINIT] DataSourceEc2.py[WARNING]:
'http://169.254.169.254/2009-04-04/meta-data/instance-id' failed [101/120s]: url
error [timed out]
>>>> Dec 9 01:19:34 vm-17-184 [CLOUDINIT] DataSourceEc2.py[WARNING]:
'http://169.254.169.254/2009-04-04/meta-data/instance-id' failed [119/120s]: url
error [timed out]
>>>> Dec 9 01:19:35 vm-17-184 [CLOUDINIT] DataSourceEc2.py[CRITICAL]: giving
up on md after 120 seconds
>>>> Dec 9 01:19:35 vm-17-184 [CLOUDINIT] __init__.py[DEBUG]: Did not find
data source. searched classes: ['DataSourceNoCloudNet',
'DataSourceConfigDriveNet', 'DataSourceOVFNet', 'DataSourceEc2']
>>>> Dec 9 01:53:25 vm-17-184 [CLOUDINIT] cloud-init[INFO]: cloud-init
start-local running: Sat, 08 Dec 2012 23:53:25 +0000. up 14.37 seconds
>>>> Dec 9 01:53:25 vm-17-184 [CLOUDINIT] __init__.py[DEBUG]: searching for
data source in ['DataSourceNoCloud', 'DataSourceConfigDrive',
'DataSourceOVF']
>>>> Dec 9 01:53:25 vm-17-184 [CLOUDINIT] __init__.py[DEBUG]: Did not find
data source. searched classes: ['DataSourceNoCloud',
'DataSourceConfigDrive', 'DataSourceOVF']
>>>> Dec 9 01:53:25 vm-17-184 [CLOUDINIT] cloud-init[INFO]: cloud-init start
running: Sat, 08 Dec 2012 23:53:25 +0000. up 14.83 seconds
>>>> Dec 9 01:53:25 vm-17-184 [CLOUDINIT] __init__.py[DEBUG]: searching for
data source in ['DataSourceNoCloudNet', 'DataSourceConfigDriveNet',
'DataSourceOVFNet', 'DataSourceEc2']
>>>> Dec 9 01:53:27 vm-17-184 [CLOUDINIT] DataSourceEc2.py[DEBUG]: removed
the following from metadata urls: ['http://instance-data:8773']
>>>> Dec 9 01:54:18 vm-17-184 [CLOUDINIT] DataSourceEc2.py[WARNING]:
'http://169.254.169.254/2009-04-04/meta-data/instance-id' failed [50/120s]: url
error [timed out]
>>>> Dec 9 01:55:09 vm-17-184 [CLOUDINIT] DataSourceEc2.py[WARNING]:
'http://169.254.169.254/2009-04-04/meta-data/instance-id' failed [101/120s]: url
error [timed out]
>>>> Dec 9 01:55:27 vm-17-184 [CLOUDINIT] DataSourceEc2.py[WARNING]:
'http://169.254.169.254/2009-04-04/meta-data/instance-id' failed [119/120s]: url
error [timed out]
>>>> Dec 9 01:55:28 vm-17-184 [CLOUDINIT] DataSourceEc2.py[CRITICAL]: giving
up on md after 120 seconds
>>>> Dec 9 01:55:28 vm-17-184 [CLOUDINIT] __init__.py[DEBUG]: Did not find
data source. searched classes: ['DataSourceNoCloudNet',
'DataSourceConfigDriveNet', 'DataSourceOVFNet', 'DataSourceEc2']
>>>> Dec 9 02:13:35 vm-17-184 [CLOUDINIT] cloud-init[INFO]: cloud-init
start-local running: Sun, 09 Dec 2012 00:13:35 +0000. up 11.82 seconds
>>>> Dec 9 02:13:35 vm-17-184 [CLOUDINIT] __init__.py[DEBUG]: searching for
data source in ['DataSourceNoCloud', 'DataSourceConfigDrive',
'DataSourceOVF']
>>>> Dec 9 02:13:36 vm-17-184 [CLOUDINIT] __init__.py[DEBUG]: Did not find
data source. searched classes: ['DataSourceNoCloud',
'DataSourceConfigDrive', 'DataSourceOVF']
>>>> Dec 9 02:13:36 vm-17-184 [CLOUDINIT] cloud-init[INFO]: cloud-init start
running: Sun, 09 Dec 2012 00:13:36 +0000. up 12.31 seconds
>>>> Dec 9 02:13:36 vm-17-184 [CLOUDINIT] __init__.py[DEBUG]: searching for
data source in ['DataSourceNoCloudNet', 'DataSourceConfigDriveNet',
'DataSourceOVFNet', 'DataSourceEc2']
>>>> Dec 9 02:13:36 vm-17-184 [CLOUDINIT] DataSourceEc2.py[DEBUG]: removed
the following from metadata urls: ['http://instance-data:8773']
>>>> Dec 9 02:14:26 vm-17-184 [CLOUDINIT] DataSourceEc2.py[WARNING]:
'http://169.254.169.254/2009-04-04/meta-data/instance-id' failed [50/120s]: url
error [timed out]
>>>> Dec 9 02:15:17 vm-17-184 [CLOUDINIT] DataSourceEc2.py[WARNING]:
'http://169.254.169.254/2009-04-04/meta-data/instance-id' failed [101/120s]: url
error [timed out]
>>>> Dec 9 02:15:35 vm-17-184 [CLOUDINIT] DataSourceEc2.py[WARNING]:
'http://169.254.169.254/2009-04-04/meta-data/instance-id' failed [119/120s]: url
error [timed out]
>>>> Dec 9 02:15:36 vm-17-184 [CLOUDINIT] DataSourceEc2.py[CRITICAL]: giving
up on md after 120 seconds
>>>> Dec 9 02:15:36 vm-17-184 [CLOUDINIT] __init__.py[DEBUG]: Did not find
data source. searched classes: ['DataSourceNoCloudNet',
'DataSourceConfigDriveNet', 'DataSourceOVFNet', 'DataSourceEc2']
11 a.m.
On 10.12.12 10:55, jvlcek wrote:
Shahar,
It's complaining about the ec2-user not being there?
Are you specifying the ec2-user in the cloud-init.conf file or are you just
using root?
No,
Where is this file suppose to be?
The version of cloud-init you are using is also a bit old. The user
creation/
default user handling has changed. We are targeting cloud-init-0.7.1-2 for
RHEL6.4
I will try that with Fedora 18 which have cloud-init-0.7.1-1
Joe
On 12/10/2012 09:38 AM, Shahar Havivi wrote:
> On 10.12.12 09:11, jvlcek wrote:
>> Shahar,
>>
>> Are you launching on EC2 or a different cloud backend?
> No, I am testing on oVirt.
> The log is different now, and there is some exception regarding
> apply_credentials().
> Attaching the new log, look at the last run where the lines starts with:
> Dec 10 16:31:12 vm-17-184
>
> Thank you,
> Shahar.
>> If EC2, I am not sure, but I don't think you can set an VM's IP address
>> on EC2. So you might be encountering an EC2 issue.
>>
>> It looks as if you are not using user-data alone but the yaml formated
>> meta-data, which user-data can be a part of, in a iso or vfat filesystem
>> with a known label.
>>
>> The log below may be from one of your earlier runs, before you
>> started using genisoimage to pass in the meta-data. Does the lates
>> log file and shed any light on the IP address issue?
>>
>> I'm not overly familiar with it but I know there is a utility in
cloud-utils
>> called 'cloud-localds' [1] that creates a iso or vfat. the --help
>> output will
>> give example usage, and you can look at the created disk image.
>>
>> If you are launching on Openstack it uses the data source:
>> "config-drive-v2",
>> which is an option for passing metadata to instances in OpenStack folsom
>> and later (doc added at [2])
>>
>> [1]
>>
http://bazaar.launchpad.net/~cloud-utils-dev/cloud-utils/trunk/view/head:...
>>
>> [2] https://review.openstack.org/#/c/16504/
>>
>>
>> Hope this helps and let me know what the latest log file shows if you
>> need more help.
>>
>> Joe
>>
>> On 12/10/2012 06:31 AM, Shahar Havivi wrote:
>>> Hi,
>>> I had a little progress but still I have a questions.
>>> I can set the hostname but not the ip:
>>> meta-data:
>>> instance-id: iid-test4
>>> local-hostname: test4
>>> local-ipv4: 192.168.1.1
>>>
>>> the ip field is ignored...
>>> what interface does the ip suppose to set if I have a few?
>>>
>>>
>>> On 09.12.12 16:21, Shahar Havivi wrote:
>>>> Update:
>>>> I manage to change the host name when I generate the iso via:
>>>> $ genisoimage -output seed.iso -volid cidata -joliet -rock user-data
meta-data
>>>>
>>>> On 09.12.12 15:23, Shahar Havivi wrote:
>>>>> Hi,
>>>>> I am trying to configure RHEL 6.3 via cloud-init.
>>>>> I am using cloud-init-0.6.3-0.7.bzr532.el6.noarch package and have a
RHEL 6.3
>>>>> guest os.
>>>>>
>>>>> iso format ant label are:
>>>>> [root@vm-17-184 cloudinit]# blkid /dev/sr0
>>>>> /dev/sr0: LABEL="cidata" TYPE="iso9660"
>>>>>
>>>>> iso file content:
>>>>> [root@vm-17-184 cdrom]# cat meta-data
>>>>> instance-id: iid-abcdefg
>>>>> network-interfaces: |
>>>>> iface eth0 inet static
>>>>> address 192.168.1.10
>>>>> network 192.168.1.0
>>>>> netmask 255.255.255.0
>>>>> broadcast 192.168.1.255
>>>>> gateway 192.168.1.254
>>>>>
>>>>> and I try the user-data file:
>>>>> [root@vm-17-184 ~]# cat cdrom/user-data
>>>>> hostname: mynode
>>>>> fqdn: mynode.example.com
>>>>> manage_etc_hosts: true
>>>>>
>>>>>
>>>>> There is no effect on the IP address or host name, am I doing
something wrong?
>>>>>
>>>>> Attached the cloud-init.log
>>>>> Thank you,
>>>>> Shahar Havivi.
>>>>> Dec 6 06:07:18 vm-17-184 [CLOUDINIT] cloud-init[INFO]: cloud-init
start-local running: Thu, 06 Dec 2012 04:07:18 +0000. up 13.90 seconds
>>>>> Dec 6 06:07:19 vm-17-184 [CLOUDINIT] __init__.py[DEBUG]: searching
for data source in ['DataSourceNoCloud', 'DataSourceConfigDrive',
'DataSourceOVF']
>>>>> Dec 6 06:07:19 vm-17-184 [CLOUDINIT] __init__.py[DEBUG]: Did not
find data source. searched classes: ['DataSourceNoCloud',
'DataSourceConfigDrive', 'DataSourceOVF']
>>>>> Dec 6 06:07:19 vm-17-184 [CLOUDINIT] cloud-init[INFO]: cloud-init
start running: Thu, 06 Dec 2012 04:07:19 +0000. up 14.63 seconds
>>>>> Dec 6 06:07:19 vm-17-184 [CLOUDINIT] __init__.py[DEBUG]: searching
for data source in ['DataSourceNoCloudNet', 'DataSourceConfigDriveNet',
'DataSourceOVFNet', 'DataSourceEc2']
>>>>> Dec 6 06:07:19 vm-17-184 [CLOUDINIT] DataSourceEc2.py[DEBUG]:
removed the following from metadata urls: ['http://instance-data:8773']
>>>>> Dec 6 06:08:09 vm-17-184 [CLOUDINIT] DataSourceEc2.py[WARNING]:
'http://169.254.169.254/2009-04-04/meta-data/instance-id' failed [50/120s]: url
error [timed out]
>>>>> Dec 6 06:09:00 vm-17-184 [CLOUDINIT] DataSourceEc2.py[WARNING]:
'http://169.254.169.254/2009-04-04/meta-data/instance-id' failed [101/120s]: url
error [timed out]
>>>>> Dec 6 06:09:18 vm-17-184 [CLOUDINIT] DataSourceEc2.py[WARNING]:
'http://169.254.169.254/2009-04-04/meta-data/instance-id' failed [119/120s]: url
error [timed out]
>>>>> Dec 6 06:09:19 vm-17-184 [CLOUDINIT] DataSourceEc2.py[CRITICAL]:
giving up on md after 120 seconds
>>>>> Dec 6 06:09:19 vm-17-184 [CLOUDINIT] __init__.py[DEBUG]: Did not
find data source. searched classes: ['DataSourceNoCloudNet',
'DataSourceConfigDriveNet', 'DataSourceOVFNet', 'DataSourceEc2']
>>>>> Dec 9 01:17:32 vm-17-184 [CLOUDINIT] cloud-init[INFO]: cloud-init
start-local running: Sat, 08 Dec 2012 23:17:32 +0000. up 13.67 seconds
>>>>> Dec 9 01:17:32 vm-17-184 [CLOUDINIT] __init__.py[DEBUG]: searching
for data source in ['DataSourceNoCloud', 'DataSourceConfigDrive',
'DataSourceOVF']
>>>>> Dec 9 01:17:32 vm-17-184 [CLOUDINIT] __init__.py[DEBUG]: Did not
find data source. searched classes: ['DataSourceNoCloud',
'DataSourceConfigDrive', 'DataSourceOVF']
>>>>> Dec 9 01:17:33 vm-17-184 [CLOUDINIT] cloud-init[INFO]: cloud-init
start running: Sat, 08 Dec 2012 23:17:33 +0000. up 14.12 seconds
>>>>> Dec 9 01:17:33 vm-17-184 [CLOUDINIT] __init__.py[DEBUG]: searching
for data source in ['DataSourceNoCloudNet', 'DataSourceConfigDriveNet',
'DataSourceOVFNet', 'DataSourceEc2']
>>>>> Dec 9 01:17:35 vm-17-184 [CLOUDINIT] DataSourceEc2.py[DEBUG]:
removed the following from metadata urls: ['http://instance-data:8773']
>>>>> Dec 9 01:18:25 vm-17-184 [CLOUDINIT] DataSourceEc2.py[WARNING]:
'http://169.254.169.254/2009-04-04/meta-data/instance-id' failed [50/120s]: url
error [timed out]
>>>>> Dec 9 01:19:16 vm-17-184 [CLOUDINIT] DataSourceEc2.py[WARNING]:
'http://169.254.169.254/2009-04-04/meta-data/instance-id' failed [101/120s]: url
error [timed out]
>>>>> Dec 9 01:19:34 vm-17-184 [CLOUDINIT] DataSourceEc2.py[WARNING]:
'http://169.254.169.254/2009-04-04/meta-data/instance-id' failed [119/120s]: url
error [timed out]
>>>>> Dec 9 01:19:35 vm-17-184 [CLOUDINIT] DataSourceEc2.py[CRITICAL]:
giving up on md after 120 seconds
>>>>> Dec 9 01:19:35 vm-17-184 [CLOUDINIT] __init__.py[DEBUG]: Did not
find data source. searched classes: ['DataSourceNoCloudNet',
'DataSourceConfigDriveNet', 'DataSourceOVFNet', 'DataSourceEc2']
>>>>> Dec 9 01:53:25 vm-17-184 [CLOUDINIT] cloud-init[INFO]: cloud-init
start-local running: Sat, 08 Dec 2012 23:53:25 +0000. up 14.37 seconds
>>>>> Dec 9 01:53:25 vm-17-184 [CLOUDINIT] __init__.py[DEBUG]: searching
for data source in ['DataSourceNoCloud', 'DataSourceConfigDrive',
'DataSourceOVF']
>>>>> Dec 9 01:53:25 vm-17-184 [CLOUDINIT] __init__.py[DEBUG]: Did not
find data source. searched classes: ['DataSourceNoCloud',
'DataSourceConfigDrive', 'DataSourceOVF']
>>>>> Dec 9 01:53:25 vm-17-184 [CLOUDINIT] cloud-init[INFO]: cloud-init
start running: Sat, 08 Dec 2012 23:53:25 +0000. up 14.83 seconds
>>>>> Dec 9 01:53:25 vm-17-184 [CLOUDINIT] __init__.py[DEBUG]: searching
for data source in ['DataSourceNoCloudNet', 'DataSourceConfigDriveNet',
'DataSourceOVFNet', 'DataSourceEc2']
>>>>> Dec 9 01:53:27 vm-17-184 [CLOUDINIT] DataSourceEc2.py[DEBUG]:
removed the following from metadata urls: ['http://instance-data:8773']
>>>>> Dec 9 01:54:18 vm-17-184 [CLOUDINIT] DataSourceEc2.py[WARNING]:
'http://169.254.169.254/2009-04-04/meta-data/instance-id' failed [50/120s]: url
error [timed out]
>>>>> Dec 9 01:55:09 vm-17-184 [CLOUDINIT] DataSourceEc2.py[WARNING]:
'http://169.254.169.254/2009-04-04/meta-data/instance-id' failed [101/120s]: url
error [timed out]
>>>>> Dec 9 01:55:27 vm-17-184 [CLOUDINIT] DataSourceEc2.py[WARNING]:
'http://169.254.169.254/2009-04-04/meta-data/instance-id' failed [119/120s]: url
error [timed out]
>>>>> Dec 9 01:55:28 vm-17-184 [CLOUDINIT] DataSourceEc2.py[CRITICAL]:
giving up on md after 120 seconds
>>>>> Dec 9 01:55:28 vm-17-184 [CLOUDINIT] __init__.py[DEBUG]: Did not
find data source. searched classes: ['DataSourceNoCloudNet',
'DataSourceConfigDriveNet', 'DataSourceOVFNet', 'DataSourceEc2']
>>>>> Dec 9 02:13:35 vm-17-184 [CLOUDINIT] cloud-init[INFO]: cloud-init
start-local running: Sun, 09 Dec 2012 00:13:35 +0000. up 11.82 seconds
>>>>> Dec 9 02:13:35 vm-17-184 [CLOUDINIT] __init__.py[DEBUG]: searching
for data source in ['DataSourceNoCloud', 'DataSourceConfigDrive',
'DataSourceOVF']
>>>>> Dec 9 02:13:36 vm-17-184 [CLOUDINIT] __init__.py[DEBUG]: Did not
find data source. searched classes: ['DataSourceNoCloud',
'DataSourceConfigDrive', 'DataSourceOVF']
>>>>> Dec 9 02:13:36 vm-17-184 [CLOUDINIT] cloud-init[INFO]: cloud-init
start running: Sun, 09 Dec 2012 00:13:36 +0000. up 12.31 seconds
>>>>> Dec 9 02:13:36 vm-17-184 [CLOUDINIT] __init__.py[DEBUG]: searching
for data source in ['DataSourceNoCloudNet', 'DataSourceConfigDriveNet',
'DataSourceOVFNet', 'DataSourceEc2']
>>>>> Dec 9 02:13:36 vm-17-184 [CLOUDINIT] DataSourceEc2.py[DEBUG]:
removed the following from metadata urls: ['http://instance-data:8773']
>>>>> Dec 9 02:14:26 vm-17-184 [CLOUDINIT] DataSourceEc2.py[WARNING]:
'http://169.254.169.254/2009-04-04/meta-data/instance-id' failed [50/120s]: url
error [timed out]
>>>>> Dec 9 02:15:17 vm-17-184 [CLOUDINIT] DataSourceEc2.py[WARNING]:
'http://169.254.169.254/2009-04-04/meta-data/instance-id' failed [101/120s]: url
error [timed out]
>>>>> Dec 9 02:15:35 vm-17-184 [CLOUDINIT] DataSourceEc2.py[WARNING]:
'http://169.254.169.254/2009-04-04/meta-data/instance-id' failed [119/120s]: url
error [timed out]
>>>>> Dec 9 02:15:36 vm-17-184 [CLOUDINIT] DataSourceEc2.py[CRITICAL]:
giving up on md after 120 seconds
>>>>> Dec 9 02:15:36 vm-17-184 [CLOUDINIT] __init__.py[DEBUG]: Did not
find data source. searched classes: ['DataSourceNoCloudNet',
'DataSourceConfigDriveNet', 'DataSourceOVFNet', 'DataSourceEc2']
11:03 a.m.
On 12/10/2012 12:00 PM, Shahar Havivi wrote:
On 10.12.12 10:55, jvlcek wrote:
> Shahar,
>
> It's complaining about the ec2-user not being there?
>
> Are you specifying the ec2-user in the cloud-init.conf file or are you just
> using root?
No,
Where is this file suppose to be?
That version of cloud-init should be released with the RHEL 6.4 public
beta last week.
It could be that the file is not properly showing up on the beta
channel. If you have access to the 6.4 Beta channels, there's the core
channel, optional, supplementary and then there should be a new RHEL
Common channel where cloud-init lives.
Can you see if you have access to this channel?
(adding some add'l folks to help with details on how to get access to
that channel)
Perry
>
> The version of cloud-init you are using is also a bit old. The user
> creation/
> default user handling has changed. We are targeting cloud-init-0.7.1-2 for
> RHEL6.4
I will try that with Fedora 18 which have cloud-init-0.7.1-1
>
> Joe
>
>
> On 12/10/2012 09:38 AM, Shahar Havivi wrote:
>> On 10.12.12 09:11, jvlcek wrote:
>>> Shahar,
>>>
>>> Are you launching on EC2 or a different cloud backend?
>> No, I am testing on oVirt.
>> The log is different now, and there is some exception regarding
>> apply_credentials().
>> Attaching the new log, look at the last run where the lines starts with:
>> Dec 10 16:31:12 vm-17-184
>>
>> Thank you,
>> Shahar.
>>> If EC2, I am not sure, but I don't think you can set an VM's IP
address
>>> on EC2. So you might be encountering an EC2 issue.
>>>
>>> It looks as if you are not using user-data alone but the yaml formated
>>> meta-data, which user-data can be a part of, in a iso or vfat filesystem
>>> with a known label.
>>>
>>> The log below may be from one of your earlier runs, before you
>>> started using genisoimage to pass in the meta-data. Does the lates
>>> log file and shed any light on the IP address issue?
>>>
>>> I'm not overly familiar with it but I know there is a utility in
cloud-utils
>>> called 'cloud-localds' [1] that creates a iso or vfat. the --help
>>> output will
>>> give example usage, and you can look at the created disk image.
>>>
>>> If you are launching on Openstack it uses the data source:
>>> "config-drive-v2",
>>> which is an option for passing metadata to instances in OpenStack folsom
>>> and later (doc added at [2])
>>>
>>> [1]
>>>
http://bazaar.launchpad.net/~cloud-utils-dev/cloud-utils/trunk/view/head:...
>>>
>>> [2] https://review.openstack.org/#/c/16504/
>>>
>>>
>>> Hope this helps and let me know what the latest log file shows if you
>>> need more help.
>>>
>>> Joe
>>>
>>> On 12/10/2012 06:31 AM, Shahar Havivi wrote:
>>>> Hi,
>>>> I had a little progress but still I have a questions.
>>>> I can set the hostname but not the ip:
>>>> meta-data:
>>>> instance-id: iid-test4
>>>> local-hostname: test4
>>>> local-ipv4: 192.168.1.1
>>>>
>>>> the ip field is ignored...
>>>> what interface does the ip suppose to set if I have a few?
>>>>
>>>>
>>>> On 09.12.12 16:21, Shahar Havivi wrote:
>>>>> Update:
>>>>> I manage to change the host name when I generate the iso via:
>>>>> $ genisoimage -output seed.iso -volid cidata -joliet -rock user-data
meta-data
>>>>>
>>>>> On 09.12.12 15:23, Shahar Havivi wrote:
>>>>>> Hi,
>>>>>> I am trying to configure RHEL 6.3 via cloud-init.
>>>>>> I am using cloud-init-0.6.3-0.7.bzr532.el6.noarch package and
have a RHEL 6.3
>>>>>> guest os.
>>>>>>
>>>>>> iso format ant label are:
>>>>>> [root@vm-17-184 cloudinit]# blkid /dev/sr0
>>>>>> /dev/sr0: LABEL="cidata" TYPE="iso9660"
>>>>>>
>>>>>> iso file content:
>>>>>> [root@vm-17-184 cdrom]# cat meta-data
>>>>>> instance-id: iid-abcdefg
>>>>>> network-interfaces: |
>>>>>> iface eth0 inet static
>>>>>> address 192.168.1.10
>>>>>> network 192.168.1.0
>>>>>> netmask 255.255.255.0
>>>>>> broadcast 192.168.1.255
>>>>>> gateway 192.168.1.254
>>>>>>
>>>>>> and I try the user-data file:
>>>>>> [root@vm-17-184 ~]# cat cdrom/user-data
>>>>>> hostname: mynode
>>>>>> fqdn: mynode.example.com
>>>>>> manage_etc_hosts: true
>>>>>>
>>>>>>
>>>>>> There is no effect on the IP address or host name, am I doing
something wrong?
>>>>>>
>>>>>> Attached the cloud-init.log
>>>>>> Thank you,
>>>>>> Shahar Havivi.
>>>>>> Dec 6 06:07:18 vm-17-184 [CLOUDINIT] cloud-init[INFO]:
cloud-init start-local running: Thu, 06 Dec 2012 04:07:18 +0000. up 13.90 seconds
>>>>>> Dec 6 06:07:19 vm-17-184 [CLOUDINIT] __init__.py[DEBUG]:
searching for data source in ['DataSourceNoCloud',
'DataSourceConfigDrive', 'DataSourceOVF']
>>>>>> Dec 6 06:07:19 vm-17-184 [CLOUDINIT] __init__.py[DEBUG]: Did not
find data source. searched classes: ['DataSourceNoCloud',
'DataSourceConfigDrive', 'DataSourceOVF']
>>>>>> Dec 6 06:07:19 vm-17-184 [CLOUDINIT] cloud-init[INFO]:
cloud-init start running: Thu, 06 Dec 2012 04:07:19 +0000. up 14.63 seconds
>>>>>> Dec 6 06:07:19 vm-17-184 [CLOUDINIT] __init__.py[DEBUG]:
searching for data source in ['DataSourceNoCloudNet',
'DataSourceConfigDriveNet', 'DataSourceOVFNet', 'DataSourceEc2']
>>>>>> Dec 6 06:07:19 vm-17-184 [CLOUDINIT] DataSourceEc2.py[DEBUG]:
removed the following from metadata urls: ['http://instance-data:8773']
>>>>>> Dec 6 06:08:09 vm-17-184 [CLOUDINIT] DataSourceEc2.py[WARNING]:
'http://169.254.169.254/2009-04-04/meta-data/instance-id' failed [50/120s]: url
error [timed out]
>>>>>> Dec 6 06:09:00 vm-17-184 [CLOUDINIT] DataSourceEc2.py[WARNING]:
'http://169.254.169.254/2009-04-04/meta-data/instance-id' failed [101/120s]: url
error [timed out]
>>>>>> Dec 6 06:09:18 vm-17-184 [CLOUDINIT] DataSourceEc2.py[WARNING]:
'http://169.254.169.254/2009-04-04/meta-data/instance-id' failed [119/120s]: url
error [timed out]
>>>>>> Dec 6 06:09:19 vm-17-184 [CLOUDINIT] DataSourceEc2.py[CRITICAL]:
giving up on md after 120 seconds
>>>>>> Dec 6 06:09:19 vm-17-184 [CLOUDINIT] __init__.py[DEBUG]: Did not
find data source. searched classes: ['DataSourceNoCloudNet',
'DataSourceConfigDriveNet', 'DataSourceOVFNet', 'DataSourceEc2']
>>>>>> Dec 9 01:17:32 vm-17-184 [CLOUDINIT] cloud-init[INFO]:
cloud-init start-local running: Sat, 08 Dec 2012 23:17:32 +0000. up 13.67 seconds
>>>>>> Dec 9 01:17:32 vm-17-184 [CLOUDINIT] __init__.py[DEBUG]:
searching for data source in ['DataSourceNoCloud',
'DataSourceConfigDrive', 'DataSourceOVF']
>>>>>> Dec 9 01:17:32 vm-17-184 [CLOUDINIT] __init__.py[DEBUG]: Did not
find data source. searched classes: ['DataSourceNoCloud',
'DataSourceConfigDrive', 'DataSourceOVF']
>>>>>> Dec 9 01:17:33 vm-17-184 [CLOUDINIT] cloud-init[INFO]:
cloud-init start running: Sat, 08 Dec 2012 23:17:33 +0000. up 14.12 seconds
>>>>>> Dec 9 01:17:33 vm-17-184 [CLOUDINIT] __init__.py[DEBUG]:
searching for data source in ['DataSourceNoCloudNet',
'DataSourceConfigDriveNet', 'DataSourceOVFNet', 'DataSourceEc2']
>>>>>> Dec 9 01:17:35 vm-17-184 [CLOUDINIT] DataSourceEc2.py[DEBUG]:
removed the following from metadata urls: ['http://instance-data:8773']
>>>>>> Dec 9 01:18:25 vm-17-184 [CLOUDINIT] DataSourceEc2.py[WARNING]:
'http://169.254.169.254/2009-04-04/meta-data/instance-id' failed [50/120s]: url
error [timed out]
>>>>>> Dec 9 01:19:16 vm-17-184 [CLOUDINIT] DataSourceEc2.py[WARNING]:
'http://169.254.169.254/2009-04-04/meta-data/instance-id' failed [101/120s]: url
error [timed out]
>>>>>> Dec 9 01:19:34 vm-17-184 [CLOUDINIT] DataSourceEc2.py[WARNING]:
'http://169.254.169.254/2009-04-04/meta-data/instance-id' failed [119/120s]: url
error [timed out]
>>>>>> Dec 9 01:19:35 vm-17-184 [CLOUDINIT] DataSourceEc2.py[CRITICAL]:
giving up on md after 120 seconds
>>>>>> Dec 9 01:19:35 vm-17-184 [CLOUDINIT] __init__.py[DEBUG]: Did not
find data source. searched classes: ['DataSourceNoCloudNet',
'DataSourceConfigDriveNet', 'DataSourceOVFNet', 'DataSourceEc2']
>>>>>> Dec 9 01:53:25 vm-17-184 [CLOUDINIT] cloud-init[INFO]:
cloud-init start-local running: Sat, 08 Dec 2012 23:53:25 +0000. up 14.37 seconds
>>>>>> Dec 9 01:53:25 vm-17-184 [CLOUDINIT] __init__.py[DEBUG]:
searching for data source in ['DataSourceNoCloud',
'DataSourceConfigDrive', 'DataSourceOVF']
>>>>>> Dec 9 01:53:25 vm-17-184 [CLOUDINIT] __init__.py[DEBUG]: Did not
find data source. searched classes: ['DataSourceNoCloud',
'DataSourceConfigDrive', 'DataSourceOVF']
>>>>>> Dec 9 01:53:25 vm-17-184 [CLOUDINIT] cloud-init[INFO]:
cloud-init start running: Sat, 08 Dec 2012 23:53:25 +0000. up 14.83 seconds
>>>>>> Dec 9 01:53:25 vm-17-184 [CLOUDINIT] __init__.py[DEBUG]:
searching for data source in ['DataSourceNoCloudNet',
'DataSourceConfigDriveNet', 'DataSourceOVFNet', 'DataSourceEc2']
>>>>>> Dec 9 01:53:27 vm-17-184 [CLOUDINIT] DataSourceEc2.py[DEBUG]:
removed the following from metadata urls: ['http://instance-data:8773']
>>>>>> Dec 9 01:54:18 vm-17-184 [CLOUDINIT] DataSourceEc2.py[WARNING]:
'http://169.254.169.254/2009-04-04/meta-data/instance-id' failed [50/120s]: url
error [timed out]
>>>>>> Dec 9 01:55:09 vm-17-184 [CLOUDINIT] DataSourceEc2.py[WARNING]:
'http://169.254.169.254/2009-04-04/meta-data/instance-id' failed [101/120s]: url
error [timed out]
>>>>>> Dec 9 01:55:27 vm-17-184 [CLOUDINIT] DataSourceEc2.py[WARNING]:
'http://169.254.169.254/2009-04-04/meta-data/instance-id' failed [119/120s]: url
error [timed out]
>>>>>> Dec 9 01:55:28 vm-17-184 [CLOUDINIT] DataSourceEc2.py[CRITICAL]:
giving up on md after 120 seconds
>>>>>> Dec 9 01:55:28 vm-17-184 [CLOUDINIT] __init__.py[DEBUG]: Did not
find data source. searched classes: ['DataSourceNoCloudNet',
'DataSourceConfigDriveNet', 'DataSourceOVFNet', 'DataSourceEc2']
>>>>>> Dec 9 02:13:35 vm-17-184 [CLOUDINIT] cloud-init[INFO]:
cloud-init start-local running: Sun, 09 Dec 2012 00:13:35 +0000. up 11.82 seconds
>>>>>> Dec 9 02:13:35 vm-17-184 [CLOUDINIT] __init__.py[DEBUG]:
searching for data source in ['DataSourceNoCloud',
'DataSourceConfigDrive', 'DataSourceOVF']
>>>>>> Dec 9 02:13:36 vm-17-184 [CLOUDINIT] __init__.py[DEBUG]: Did not
find data source. searched classes: ['DataSourceNoCloud',
'DataSourceConfigDrive', 'DataSourceOVF']
>>>>>> Dec 9 02:13:36 vm-17-184 [CLOUDINIT] cloud-init[INFO]:
cloud-init start running: Sun, 09 Dec 2012 00:13:36 +0000. up 12.31 seconds
>>>>>> Dec 9 02:13:36 vm-17-184 [CLOUDINIT] __init__.py[DEBUG]:
searching for data source in ['DataSourceNoCloudNet',
'DataSourceConfigDriveNet', 'DataSourceOVFNet', 'DataSourceEc2']
>>>>>> Dec 9 02:13:36 vm-17-184 [CLOUDINIT] DataSourceEc2.py[DEBUG]:
removed the following from metadata urls: ['http://instance-data:8773']
>>>>>> Dec 9 02:14:26 vm-17-184 [CLOUDINIT] DataSourceEc2.py[WARNING]:
'http://169.254.169.254/2009-04-04/meta-data/instance-id' failed [50/120s]: url
error [timed out]
>>>>>> Dec 9 02:15:17 vm-17-184 [CLOUDINIT] DataSourceEc2.py[WARNING]:
'http://169.254.169.254/2009-04-04/meta-data/instance-id' failed [101/120s]: url
error [timed out]
>>>>>> Dec 9 02:15:35 vm-17-184 [CLOUDINIT] DataSourceEc2.py[WARNING]:
'http://169.254.169.254/2009-04-04/meta-data/instance-id' failed [119/120s]: url
error [timed out]
>>>>>> Dec 9 02:15:36 vm-17-184 [CLOUDINIT] DataSourceEc2.py[CRITICAL]:
giving up on md after 120 seconds
>>>>>> Dec 9 02:15:36 vm-17-184 [CLOUDINIT] __init__.py[DEBUG]: Did not
find data source. searched classes: ['DataSourceNoCloudNet',
'DataSourceConfigDriveNet', 'DataSourceOVFNet', 'DataSourceEc2']
>
11:07 a.m.
On 10.12.12 12:03, Perry Myers wrote:
On 12/10/2012 12:00 PM, Shahar Havivi wrote:
> On 10.12.12 10:55, jvlcek wrote:
>> Shahar,
>>
>> It's complaining about the ec2-user not being there?
>>
>> Are you specifying the ec2-user in the cloud-init.conf file or are you just
>> using root?
> No,
> Where is this file suppose to be?
That version of cloud-init should be released with the RHEL 6.4 public
beta last week.
It could be that the file is not properly showing up on the beta
channel. If you have access to the 6.4 Beta channels, there's the core
channel, optional, supplementary and then there should be a new RHEL
Common channel where cloud-init lives.
Can you see if you have access to this channel?
(adding some add'l folks to help with details on how to get access to
that channel)
Perry
Thank you,
I will try to get 6.4
>>
>> The version of cloud-init you are using is also a bit old. The user
>> creation/
>> default user handling has changed. We are targeting cloud-init-0.7.1-2 for
>> RHEL6.4
> I will try that with Fedora 18 which have cloud-init-0.7.1-1
>>
>> Joe
>>
>>
>> On 12/10/2012 09:38 AM, Shahar Havivi wrote:
>>> On 10.12.12 09:11, jvlcek wrote:
>>>> Shahar,
>>>>
>>>> Are you launching on EC2 or a different cloud backend?
>>> No, I am testing on oVirt.
>>> The log is different now, and there is some exception regarding
>>> apply_credentials().
>>> Attaching the new log, look at the last run where the lines starts with:
>>> Dec 10 16:31:12 vm-17-184
>>>
>>> Thank you,
>>> Shahar.
>>>> If EC2, I am not sure, but I don't think you can set an VM's IP
address
>>>> on EC2. So you might be encountering an EC2 issue.
>>>>
>>>> It looks as if you are not using user-data alone but the yaml formated
>>>> meta-data, which user-data can be a part of, in a iso or vfat
filesystem
>>>> with a known label.
>>>>
>>>> The log below may be from one of your earlier runs, before you
>>>> started using genisoimage to pass in the meta-data. Does the lates
>>>> log file and shed any light on the IP address issue?
>>>>
>>>> I'm not overly familiar with it but I know there is a utility in
cloud-utils
>>>> called 'cloud-localds' [1] that creates a iso or vfat. the
--help
>>>> output will
>>>> give example usage, and you can look at the created disk image.
>>>>
>>>> If you are launching on Openstack it uses the data source:
>>>> "config-drive-v2",
>>>> which is an option for passing metadata to instances in OpenStack
folsom
>>>> and later (doc added at [2])
>>>>
>>>> [1]
>>>>
http://bazaar.launchpad.net/~cloud-utils-dev/cloud-utils/trunk/view/head:...
>>>>
>>>> [2] https://review.openstack.org/#/c/16504/
>>>>
>>>>
>>>> Hope this helps and let me know what the latest log file shows if you
>>>> need more help.
>>>>
>>>> Joe
>>>>
>>>> On 12/10/2012 06:31 AM, Shahar Havivi wrote:
>>>>> Hi,
>>>>> I had a little progress but still I have a questions.
>>>>> I can set the hostname but not the ip:
>>>>> meta-data:
>>>>> instance-id: iid-test4
>>>>> local-hostname: test4
>>>>> local-ipv4: 192.168.1.1
>>>>>
>>>>> the ip field is ignored...
>>>>> what interface does the ip suppose to set if I have a few?
>>>>>
>>>>>
>>>>> On 09.12.12 16:21, Shahar Havivi wrote:
>>>>>> Update:
>>>>>> I manage to change the host name when I generate the iso via:
>>>>>> $ genisoimage -output seed.iso -volid cidata -joliet -rock
user-data meta-data
>>>>>>
>>>>>> On 09.12.12 15:23, Shahar Havivi wrote:
>>>>>>> Hi,
>>>>>>> I am trying to configure RHEL 6.3 via cloud-init.
>>>>>>> I am using cloud-init-0.6.3-0.7.bzr532.el6.noarch package
and have a RHEL 6.3
>>>>>>> guest os.
>>>>>>>
>>>>>>> iso format ant label are:
>>>>>>> [root@vm-17-184 cloudinit]# blkid /dev/sr0
>>>>>>> /dev/sr0: LABEL="cidata" TYPE="iso9660"
>>>>>>>
>>>>>>> iso file content:
>>>>>>> [root@vm-17-184 cdrom]# cat meta-data
>>>>>>> instance-id: iid-abcdefg
>>>>>>> network-interfaces: |
>>>>>>> iface eth0 inet static
>>>>>>> address 192.168.1.10
>>>>>>> network 192.168.1.0
>>>>>>> netmask 255.255.255.0
>>>>>>> broadcast 192.168.1.255
>>>>>>> gateway 192.168.1.254
>>>>>>>
>>>>>>> and I try the user-data file:
>>>>>>> [root@vm-17-184 ~]# cat cdrom/user-data
>>>>>>> hostname: mynode
>>>>>>> fqdn: mynode.example.com
>>>>>>> manage_etc_hosts: true
>>>>>>>
>>>>>>>
>>>>>>> There is no effect on the IP address or host name, am I
doing something wrong?
>>>>>>>
>>>>>>> Attached the cloud-init.log
>>>>>>> Thank you,
>>>>>>> Shahar Havivi.
>>>>>>> Dec 6 06:07:18 vm-17-184 [CLOUDINIT] cloud-init[INFO]:
cloud-init start-local running: Thu, 06 Dec 2012 04:07:18 +0000. up 13.90 seconds
>>>>>>> Dec 6 06:07:19 vm-17-184 [CLOUDINIT] __init__.py[DEBUG]:
searching for data source in ['DataSourceNoCloud',
'DataSourceConfigDrive', 'DataSourceOVF']
>>>>>>> Dec 6 06:07:19 vm-17-184 [CLOUDINIT] __init__.py[DEBUG]:
Did not find data source. searched classes: ['DataSourceNoCloud',
'DataSourceConfigDrive', 'DataSourceOVF']
>>>>>>> Dec 6 06:07:19 vm-17-184 [CLOUDINIT] cloud-init[INFO]:
cloud-init start running: Thu, 06 Dec 2012 04:07:19 +0000. up 14.63 seconds
>>>>>>> Dec 6 06:07:19 vm-17-184 [CLOUDINIT] __init__.py[DEBUG]:
searching for data source in ['DataSourceNoCloudNet',
'DataSourceConfigDriveNet', 'DataSourceOVFNet', 'DataSourceEc2']
>>>>>>> Dec 6 06:07:19 vm-17-184 [CLOUDINIT]
DataSourceEc2.py[DEBUG]: removed the following from metadata urls:
['http://instance-data:8773']
>>>>>>> Dec 6 06:08:09 vm-17-184 [CLOUDINIT]
DataSourceEc2.py[WARNING]:
'http://169.254.169.254/2009-04-04/meta-data/instance-id' failed [50/120s]: url
error [timed out]
>>>>>>> Dec 6 06:09:00 vm-17-184 [CLOUDINIT]
DataSourceEc2.py[WARNING]:
'http://169.254.169.254/2009-04-04/meta-data/instance-id' failed [101/120s]: url
error [timed out]
>>>>>>> Dec 6 06:09:18 vm-17-184 [CLOUDINIT]
DataSourceEc2.py[WARNING]:
'http://169.254.169.254/2009-04-04/meta-data/instance-id' failed [119/120s]: url
error [timed out]
>>>>>>> Dec 6 06:09:19 vm-17-184 [CLOUDINIT]
DataSourceEc2.py[CRITICAL]: giving up on md after 120 seconds
>>>>>>> Dec 6 06:09:19 vm-17-184 [CLOUDINIT] __init__.py[DEBUG]:
Did not find data source. searched classes: ['DataSourceNoCloudNet',
'DataSourceConfigDriveNet', 'DataSourceOVFNet', 'DataSourceEc2']
>>>>>>> Dec 9 01:17:32 vm-17-184 [CLOUDINIT] cloud-init[INFO]:
cloud-init start-local running: Sat, 08 Dec 2012 23:17:32 +0000. up 13.67 seconds
>>>>>>> Dec 9 01:17:32 vm-17-184 [CLOUDINIT] __init__.py[DEBUG]:
searching for data source in ['DataSourceNoCloud',
'DataSourceConfigDrive', 'DataSourceOVF']
>>>>>>> Dec 9 01:17:32 vm-17-184 [CLOUDINIT] __init__.py[DEBUG]:
Did not find data source. searched classes: ['DataSourceNoCloud',
'DataSourceConfigDrive', 'DataSourceOVF']
>>>>>>> Dec 9 01:17:33 vm-17-184 [CLOUDINIT] cloud-init[INFO]:
cloud-init start running: Sat, 08 Dec 2012 23:17:33 +0000. up 14.12 seconds
>>>>>>> Dec 9 01:17:33 vm-17-184 [CLOUDINIT] __init__.py[DEBUG]:
searching for data source in ['DataSourceNoCloudNet',
'DataSourceConfigDriveNet', 'DataSourceOVFNet', 'DataSourceEc2']
>>>>>>> Dec 9 01:17:35 vm-17-184 [CLOUDINIT]
DataSourceEc2.py[DEBUG]: removed the following from metadata urls:
['http://instance-data:8773']
>>>>>>> Dec 9 01:18:25 vm-17-184 [CLOUDINIT]
DataSourceEc2.py[WARNING]:
'http://169.254.169.254/2009-04-04/meta-data/instance-id' failed [50/120s]: url
error [timed out]
>>>>>>> Dec 9 01:19:16 vm-17-184 [CLOUDINIT]
DataSourceEc2.py[WARNING]:
'http://169.254.169.254/2009-04-04/meta-data/instance-id' failed [101/120s]: url
error [timed out]
>>>>>>> Dec 9 01:19:34 vm-17-184 [CLOUDINIT]
DataSourceEc2.py[WARNING]:
'http://169.254.169.254/2009-04-04/meta-data/instance-id' failed [119/120s]: url
error [timed out]
>>>>>>> Dec 9 01:19:35 vm-17-184 [CLOUDINIT]
DataSourceEc2.py[CRITICAL]: giving up on md after 120 seconds
>>>>>>> Dec 9 01:19:35 vm-17-184 [CLOUDINIT] __init__.py[DEBUG]:
Did not find data source. searched classes: ['DataSourceNoCloudNet',
'DataSourceConfigDriveNet', 'DataSourceOVFNet', 'DataSourceEc2']
>>>>>>> Dec 9 01:53:25 vm-17-184 [CLOUDINIT] cloud-init[INFO]:
cloud-init start-local running: Sat, 08 Dec 2012 23:53:25 +0000. up 14.37 seconds
>>>>>>> Dec 9 01:53:25 vm-17-184 [CLOUDINIT] __init__.py[DEBUG]:
searching for data source in ['DataSourceNoCloud',
'DataSourceConfigDrive', 'DataSourceOVF']
>>>>>>> Dec 9 01:53:25 vm-17-184 [CLOUDINIT] __init__.py[DEBUG]:
Did not find data source. searched classes: ['DataSourceNoCloud',
'DataSourceConfigDrive', 'DataSourceOVF']
>>>>>>> Dec 9 01:53:25 vm-17-184 [CLOUDINIT] cloud-init[INFO]:
cloud-init start running: Sat, 08 Dec 2012 23:53:25 +0000. up 14.83 seconds
>>>>>>> Dec 9 01:53:25 vm-17-184 [CLOUDINIT] __init__.py[DEBUG]:
searching for data source in ['DataSourceNoCloudNet',
'DataSourceConfigDriveNet', 'DataSourceOVFNet', 'DataSourceEc2']
>>>>>>> Dec 9 01:53:27 vm-17-184 [CLOUDINIT]
DataSourceEc2.py[DEBUG]: removed the following from metadata urls:
['http://instance-data:8773']
>>>>>>> Dec 9 01:54:18 vm-17-184 [CLOUDINIT]
DataSourceEc2.py[WARNING]:
'http://169.254.169.254/2009-04-04/meta-data/instance-id' failed [50/120s]: url
error [timed out]
>>>>>>> Dec 9 01:55:09 vm-17-184 [CLOUDINIT]
DataSourceEc2.py[WARNING]:
'http://169.254.169.254/2009-04-04/meta-data/instance-id' failed [101/120s]: url
error [timed out]
>>>>>>> Dec 9 01:55:27 vm-17-184 [CLOUDINIT]
DataSourceEc2.py[WARNING]:
'http://169.254.169.254/2009-04-04/meta-data/instance-id' failed [119/120s]: url
error [timed out]
>>>>>>> Dec 9 01:55:28 vm-17-184 [CLOUDINIT]
DataSourceEc2.py[CRITICAL]: giving up on md after 120 seconds
>>>>>>> Dec 9 01:55:28 vm-17-184 [CLOUDINIT] __init__.py[DEBUG]:
Did not find data source. searched classes: ['DataSourceNoCloudNet',
'DataSourceConfigDriveNet', 'DataSourceOVFNet', 'DataSourceEc2']
>>>>>>> Dec 9 02:13:35 vm-17-184 [CLOUDINIT] cloud-init[INFO]:
cloud-init start-local running: Sun, 09 Dec 2012 00:13:35 +0000. up 11.82 seconds
>>>>>>> Dec 9 02:13:35 vm-17-184 [CLOUDINIT] __init__.py[DEBUG]:
searching for data source in ['DataSourceNoCloud',
'DataSourceConfigDrive', 'DataSourceOVF']
>>>>>>> Dec 9 02:13:36 vm-17-184 [CLOUDINIT] __init__.py[DEBUG]:
Did not find data source. searched classes: ['DataSourceNoCloud',
'DataSourceConfigDrive', 'DataSourceOVF']
>>>>>>> Dec 9 02:13:36 vm-17-184 [CLOUDINIT] cloud-init[INFO]:
cloud-init start running: Sun, 09 Dec 2012 00:13:36 +0000. up 12.31 seconds
>>>>>>> Dec 9 02:13:36 vm-17-184 [CLOUDINIT] __init__.py[DEBUG]:
searching for data source in ['DataSourceNoCloudNet',
'DataSourceConfigDriveNet', 'DataSourceOVFNet', 'DataSourceEc2']
>>>>>>> Dec 9 02:13:36 vm-17-184 [CLOUDINIT]
DataSourceEc2.py[DEBUG]: removed the following from metadata urls:
['http://instance-data:8773']
>>>>>>> Dec 9 02:14:26 vm-17-184 [CLOUDINIT]
DataSourceEc2.py[WARNING]:
'http://169.254.169.254/2009-04-04/meta-data/instance-id' failed [50/120s]: url
error [timed out]
>>>>>>> Dec 9 02:15:17 vm-17-184 [CLOUDINIT]
DataSourceEc2.py[WARNING]:
'http://169.254.169.254/2009-04-04/meta-data/instance-id' failed [101/120s]: url
error [timed out]
>>>>>>> Dec 9 02:15:35 vm-17-184 [CLOUDINIT]
DataSourceEc2.py[WARNING]:
'http://169.254.169.254/2009-04-04/meta-data/instance-id' failed [119/120s]: url
error [timed out]
>>>>>>> Dec 9 02:15:36 vm-17-184 [CLOUDINIT]
DataSourceEc2.py[CRITICAL]: giving up on md after 120 seconds
>>>>>>> Dec 9 02:15:36 vm-17-184 [CLOUDINIT] __init__.py[DEBUG]:
Did not find data source. searched classes: ['DataSourceNoCloudNet',
'DataSourceConfigDriveNet', 'DataSourceOVFNet', 'DataSourceEc2']
>>
12:41 p.m.
On 12/10/2012 12:07 PM, Shahar Havivi wrote:
On 10.12.12 12:03, Perry Myers wrote:
> On 12/10/2012 12:00 PM, Shahar Havivi wrote:
>> On 10.12.12 10:55, jvlcek wrote:
>>> Shahar,
>>>
>>> It's complaining about the ec2-user not being there?
>>>
>>> Are you specifying the ec2-user in the cloud-init.conf file or are you just
>>> using root?
>> No,
>> Where is this file suppose to be?
>
> That version of cloud-init should be released with the RHEL 6.4 public
> beta last week.
>
> It could be that the file is not properly showing up on the beta
> channel. If you have access to the 6.4 Beta channels, there's the core
> channel, optional, supplementary and then there should be a new RHEL
> Common channel where cloud-init lives.
>
> Can you see if you have access to this channel?
>
> (adding some add'l folks to help with details on how to get access to
> that channel)
>
> Perry
Thank you,
I will try to get 6.4
The 6.4 Beta AMIs do not have cloud-init in them. They were targeted to,
but that didn't happen for one reason or another. They should get it in
a future snapshot, and certainly before the RC.
- Jay
12:43 p.m.
On 12/10/2012 01:41 PM, Jay Greguske wrote:
On 12/10/2012 12:07 PM, Shahar Havivi wrote:
> On 10.12.12 12:03, Perry Myers wrote:
>> On 12/10/2012 12:00 PM, Shahar Havivi wrote:
>>> On 10.12.12 10:55, jvlcek wrote:
>>>> Shahar,
>>>>
>>>> It's complaining about the ec2-user not being there?
>>>>
>>>> Are you specifying the ec2-user in the cloud-init.conf file or are you
just
>>>> using root?
>>> No,
>>> Where is this file suppose to be?
>>
>> That version of cloud-init should be released with the RHEL 6.4 public
>> beta last week.
>>
>> It could be that the file is not properly showing up on the beta
>> channel. If you have access to the 6.4 Beta channels, there's the core
>> channel, optional, supplementary and then there should be a new RHEL
>> Common channel where cloud-init lives.
>>
>> Can you see if you have access to this channel?
>>
>> (adding some add'l folks to help with details on how to get access to
>> that channel)
>>
>> Perry
> Thank you,
> I will try to get 6.4
The 6.4 Beta AMIs do not have cloud-init in them. They were targeted to,
but that didn't happen for one reason or another. They should get it in
a future snapshot, and certainly before the RC.
Ah ok. Thanks for clarifying. What about availability to just grab the
cloud-init package from the 6.4 beta channel? Should that work as well?
Shahar is working with oVirt and cloud-init, so grabbing from RHN/CDN
would be sufficient. Doesn't need to be in an AMI
Perry
1:21 p.m.
On 12/10/2012 01:43 PM, Perry Myers wrote:
On 12/10/2012 01:41 PM, Jay Greguske wrote:
> On 12/10/2012 12:07 PM, Shahar Havivi wrote:
>> On 10.12.12 12:03, Perry Myers wrote:
>>> On 12/10/2012 12:00 PM, Shahar Havivi wrote:
>>>> On 10.12.12 10:55, jvlcek wrote:
>>>>> Shahar,
>>>>>
>>>>> It's complaining about the ec2-user not being there?
>>>>>
>>>>> Are you specifying the ec2-user in the cloud-init.conf file or are
you just
>>>>> using root?
>>>> No,
>>>> Where is this file suppose to be?
>>> That version of cloud-init should be released with the RHEL 6.4 public
>>> beta last week.
>>>
>>> It could be that the file is not properly showing up on the beta
>>> channel. If you have access to the 6.4 Beta channels, there's the core
>>> channel, optional, supplementary and then there should be a new RHEL
>>> Common channel where cloud-init lives.
>>>
>>> Can you see if you have access to this channel?
>>>
>>> (adding some add'l folks to help with details on how to get access to
>>> that channel)
>>>
>>> Perry
>> Thank you,
>> I will try to get 6.4
> The 6.4 Beta AMIs do not have cloud-init in them. They were targeted to,
> but that didn't happen for one reason or another. They should get it in
> a future snapshot, and certainly before the RC.
Ah ok. Thanks for clarifying. What about availability to just grab the
cloud-init package from the 6.4 beta channel? Should that work as well?
Shahar is working with oVirt and cloud-init, so grabbing from RHN/CDN
would be sufficient. Doesn't need to be in an AMI
Perry
Shahar,
Seems you need to build new AMI. Let me know if you need help
with that.
Joe
9:06 a.m.
On 10.12.12 14:21, jvlcek wrote:
On 12/10/2012 01:43 PM, Perry Myers wrote:
> On 12/10/2012 01:41 PM, Jay Greguske wrote:
>> On 12/10/2012 12:07 PM, Shahar Havivi wrote:
>>> On 10.12.12 12:03, Perry Myers wrote:
>>>> On 12/10/2012 12:00 PM, Shahar Havivi wrote:
>>>>> On 10.12.12 10:55, jvlcek wrote:
>>>>>> Shahar,
>>>>>>
>>>>>> It's complaining about the ec2-user not being there?
>>>>>>
>>>>>> Are you specifying the ec2-user in the cloud-init.conf file or
are you just
>>>>>> using root?
>>>>> No,
>>>>> Where is this file suppose to be?
>>>> That version of cloud-init should be released with the RHEL 6.4 public
>>>> beta last week.
>>>>
>>>> It could be that the file is not properly showing up on the beta
>>>> channel. If you have access to the 6.4 Beta channels, there's the
core
>>>> channel, optional, supplementary and then there should be a new RHEL
>>>> Common channel where cloud-init lives.
>>>>
>>>> Can you see if you have access to this channel?
>>>>
>>>> (adding some add'l folks to help with details on how to get access
to
>>>> that channel)
>>>>
>>>> Perry
>>> Thank you,
>>> I will try to get 6.4
>> The 6.4 Beta AMIs do not have cloud-init in them. They were targeted to,
>> but that didn't happen for one reason or another. They should get it in
>> a future snapshot, and certainly before the RC.
> Ah ok. Thanks for clarifying. What about availability to just grab the
> cloud-init package from the 6.4 beta channel? Should that work as well?
>
> Shahar is working with oVirt and cloud-init, so grabbing from RHN/CDN
> would be sufficient. Doesn't need to be in an AMI
>
> Perry
Shahar,
Seems you need to build new AMI. Let me know if you need help
with that.
Joe
Hi,
I can't build the AMI - I am working via oVirt,
I will test it via RHEL 6.4 with the cloud-init 7.1-2.
Hope it will help
Thanks you,
Shahar Havivi.
3:29 p.m.
On Mon, 2012-12-10 at 13:43 -0500, Perry Myers wrote:
On 12/10/2012 01:41 PM, Jay Greguske wrote:
> On 12/10/2012 12:07 PM, Shahar Havivi wrote:
>> On 10.12.12 12:03, Perry Myers wrote:
>>> On 12/10/2012 12:00 PM, Shahar Havivi wrote:
>>>> On 10.12.12 10:55, jvlcek wrote:
>>>>> Shahar,
>>>>>
>>>>> It's complaining about the ec2-user not being there?
>>>>>
>>>>> Are you specifying the ec2-user in the cloud-init.conf file or are
you just
>>>>> using root?
>>>> No,
>>>> Where is this file suppose to be?
>>>
>>> That version of cloud-init should be released with the RHEL 6.4 public
>>> beta last week.
>>>
>>> It could be that the file is not properly showing up on the beta
>>> channel. If you have access to the 6.4 Beta channels, there's the core
>>> channel, optional, supplementary and then there should be a new RHEL
>>> Common channel where cloud-init lives.
>>>
>>> Can you see if you have access to this channel?
>>>
>>> (adding some add'l folks to help with details on how to get access to
>>> that channel)
>>>
>>> Perry
>> Thank you,
>> I will try to get 6.4
>
> The 6.4 Beta AMIs do not have cloud-init in them. They were targeted to,
> but that didn't happen for one reason or another. They should get it in
> a future snapshot, and certainly before the RC.
Ah ok. Thanks for clarifying. What about availability to just grab the
cloud-init package from the 6.4 beta channel? Should that work as well?
Shahar is working with oVirt and cloud-init, so grabbing from RHN/CDN
would be sufficient. Doesn't need to be in an AMI
Perry
The beta channels with cloud-init should be available through RHN
tomorrow or Monday.
Cheers
-- Dennis
8:22 p.m.
On Thu, 2012-12-13 at 16:29 -0500, Dennis Gregorovic wrote:
On Mon, 2012-12-10 at 13:43 -0500, Perry Myers wrote:
> On 12/10/2012 01:41 PM, Jay Greguske wrote:
> > On 12/10/2012 12:07 PM, Shahar Havivi wrote:
> >> On 10.12.12 12:03, Perry Myers wrote:
> >>> On 12/10/2012 12:00 PM, Shahar Havivi wrote:
> >>>> On 10.12.12 10:55, jvlcek wrote:
> >>>>> Shahar,
> >>>>>
> >>>>> It's complaining about the ec2-user not being there?
> >>>>>
> >>>>> Are you specifying the ec2-user in the cloud-init.conf file or
are you just
> >>>>> using root?
> >>>> No,
> >>>> Where is this file suppose to be?
> >>>
> >>> That version of cloud-init should be released with the RHEL 6.4 public
> >>> beta last week.
> >>>
> >>> It could be that the file is not properly showing up on the beta
> >>> channel. If you have access to the 6.4 Beta channels, there's the
core
> >>> channel, optional, supplementary and then there should be a new RHEL
> >>> Common channel where cloud-init lives.
> >>>
> >>> Can you see if you have access to this channel?
> >>>
> >>> (adding some add'l folks to help with details on how to get access
to
> >>> that channel)
> >>>
> >>> Perry
> >> Thank you,
> >> I will try to get 6.4
> >
> > The 6.4 Beta AMIs do not have cloud-init in them. They were targeted to,
> > but that didn't happen for one reason or another. They should get it in
> > a future snapshot, and certainly before the RC.
>
> Ah ok. Thanks for clarifying. What about availability to just grab the
> cloud-init package from the 6.4 beta channel? Should that work as well?
>
> Shahar is working with oVirt and cloud-init, so grabbing from RHN/CDN
> would be sufficient. Doesn't need to be in an AMI
>
> Perry
The beta channels with cloud-init should be available through RHN
tomorrow or Monday.
Cheers
-- Dennis
The channels should be available now.
-- Dennis
5:50 a.m.
On 14.12.12 21:22, Dennis Gregorovic wrote:
On Thu, 2012-12-13 at 16:29 -0500, Dennis Gregorovic wrote:
> On Mon, 2012-12-10 at 13:43 -0500, Perry Myers wrote:
> > On 12/10/2012 01:41 PM, Jay Greguske wrote:
> > > On 12/10/2012 12:07 PM, Shahar Havivi wrote:
> > >> On 10.12.12 12:03, Perry Myers wrote:
> > >>> On 12/10/2012 12:00 PM, Shahar Havivi wrote:
> > >>>> On 10.12.12 10:55, jvlcek wrote:
> > >>>>> Shahar,
> > >>>>>
> > >>>>> It's complaining about the ec2-user not being there?
> > >>>>>
> > >>>>> Are you specifying the ec2-user in the cloud-init.conf
file or are you just
> > >>>>> using root?
> > >>>> No,
> > >>>> Where is this file suppose to be?
> > >>>
> > >>> That version of cloud-init should be released with the RHEL 6.4
public
> > >>> beta last week.
> > >>>
> > >>> It could be that the file is not properly showing up on the beta
> > >>> channel. If you have access to the 6.4 Beta channels, there's
the core
> > >>> channel, optional, supplementary and then there should be a new
RHEL
> > >>> Common channel where cloud-init lives.
> > >>>
> > >>> Can you see if you have access to this channel?
> > >>>
> > >>> (adding some add'l folks to help with details on how to get
access to
> > >>> that channel)
> > >>>
> > >>> Perry
> > >> Thank you,
> > >> I will try to get 6.4
> > > > > The 6.4 Beta AMIs
do not have cloud-init in them. They were targeted to,
> > > but that didn't happen for one reason or another. They should get it
in
> > > a future snapshot, and certainly before the RC.
> > > Ah ok. Thanks for clarifying. What about
availability to just grab the
> > cloud-init package from the 6.4 beta channel? Should that work as well?
> > > Shahar is working with oVirt and cloud-init, so
grabbing from RHN/CDN
> > would be sufficient. Doesn't need to be in an AMI
> > > Perry
> The beta channels with cloud-init should be available
through RHN
> tomorrow or Monday.
> Cheers
> -- Dennis
The channels should be available now.
-- Dennis
Thank you Dennis,
I open request for RHN account and I will test it.
7:15 a.m.
On 14.12.12 21:22, Dennis Gregorovic wrote:
On Thu, 2012-12-13 at 16:29 -0500, Dennis Gregorovic wrote:
> On Mon, 2012-12-10 at 13:43 -0500, Perry Myers wrote:
> > On 12/10/2012 01:41 PM, Jay Greguske wrote:
> > > On 12/10/2012 12:07 PM, Shahar Havivi wrote:
> > >> On 10.12.12 12:03, Perry Myers wrote:
> > >>> On 12/10/2012 12:00 PM, Shahar Havivi wrote:
> > >>>> On 10.12.12 10:55, jvlcek wrote:
> > >>>>> Shahar,
> > >>>>>
> > >>>>> It's complaining about the ec2-user not being there?
> > >>>>>
> > >>>>> Are you specifying the ec2-user in the cloud-init.conf
file or are you just
> > >>>>> using root?
> > >>>> No,
> > >>>> Where is this file suppose to be?
> > >>>
> > >>> That version of cloud-init should be released with the RHEL 6.4
public
> > >>> beta last week.
> > >>>
> > >>> It could be that the file is not properly showing up on the beta
> > >>> channel. If you have access to the 6.4 Beta channels, there's
the core
> > >>> channel, optional, supplementary and then there should be a new
RHEL
> > >>> Common channel where cloud-init lives.
> > >>>
> > >>> Can you see if you have access to this channel?
> > >>>
> > >>> (adding some add'l folks to help with details on how to get
access to
> > >>> that channel)
> > >>>
> > >>> Perry
> > >> Thank you,
> > >> I will try to get 6.4
> > >
> > > The 6.4 Beta AMIs do not have cloud-init in them. They were targeted to,
> > > but that didn't happen for one reason or another. They should get it
in
> > > a future snapshot, and certainly before the RC.
> >
> > Ah ok. Thanks for clarifying. What about availability to just grab the
> > cloud-init package from the 6.4 beta channel? Should that work as well?
> >
> > Shahar is working with oVirt and cloud-init, so grabbing from RHN/CDN
> > would be sufficient. Doesn't need to be in an AMI
> >
> > Perry
>
> The beta channels with cloud-init should be available through RHN
> tomorrow or Monday.
>
> Cheers
> -- Dennis
What is the channel name that include the cloud-init (I couldn't
fine a
channel with cloud-init in its name).
The channels should be available now.
-- Dennis
7:33 a.m.
On 16.12.12 15:15, Shahar Havivi wrote:
On 14.12.12 21:22, Dennis Gregorovic wrote:
> On Thu, 2012-12-13 at 16:29 -0500, Dennis Gregorovic wrote:
> > On Mon, 2012-12-10 at 13:43 -0500, Perry Myers wrote:
> > > On 12/10/2012 01:41 PM, Jay Greguske wrote:
> > > > On 12/10/2012 12:07 PM, Shahar Havivi wrote:
> > > >> On 10.12.12 12:03, Perry Myers wrote:
> > > >>> On 12/10/2012 12:00 PM, Shahar Havivi wrote:
> > > >>>> On 10.12.12 10:55, jvlcek wrote:
> > > >>>>> Shahar,
> > > >>>>>
> > > >>>>> It's complaining about the ec2-user not being
there?
> > > >>>>>
> > > >>>>> Are you specifying the ec2-user in the
cloud-init.conf file or are you just
> > > >>>>> using root?
> > > >>>> No,
> > > >>>> Where is this file suppose to be?
> > > >>>
> > > >>> That version of cloud-init should be released with the RHEL
6.4 public
> > > >>> beta last week.
> > > >>>
> > > >>> It could be that the file is not properly showing up on the
beta
> > > >>> channel. If you have access to the 6.4 Beta channels,
there's the core
> > > >>> channel, optional, supplementary and then there should be a
new RHEL
> > > >>> Common channel where cloud-init lives.
> > > >>>
> > > >>> Can you see if you have access to this channel?
> > > >>>
> > > >>> (adding some add'l folks to help with details on how to
get access to
> > > >>> that channel)
> > > >>>
> > > >>> Perry
> > > >> Thank you,
> > > >> I will try to get 6.4
> > > >
> > > > The 6.4 Beta AMIs do not have cloud-init in them. They were targeted
to,
> > > > but that didn't happen for one reason or another. They should get
it in
> > > > a future snapshot, and certainly before the RC.
> > >
> > > Ah ok. Thanks for clarifying. What about availability to just grab the
> > > cloud-init package from the 6.4 beta channel? Should that work as well?
> > >
> > > Shahar is working with oVirt and cloud-init, so grabbing from RHN/CDN
> > > would be sufficient. Doesn't need to be in an AMI
> > >
> > > Perry
> >
> > The beta channels with cloud-init should be available through RHN
> > tomorrow or Monday.
> >
> > Cheers
> > -- Dennis
What is the channel name that include the cloud-init (I couldn't fine a
channel with cloud-init in its name).
Found it in the common channel,
I have a problem installing it because I get glibc-common dependency
mismatch...
Is there other channel that I need my host to be register to?
>
> The channels should be available now.
>
> -- Dennis
>
4:04 p.m.
On Sun, 2012-12-16 at 15:33 +0200, Shahar Havivi wrote:
On 16.12.12 15:15, Shahar Havivi wrote:
> On 14.12.12 21:22, Dennis Gregorovic wrote:
> > On Thu, 2012-12-13 at 16:29 -0500, Dennis Gregorovic wrote:
> > > On Mon, 2012-12-10 at 13:43 -0500, Perry Myers wrote:
> > > > On 12/10/2012 01:41 PM, Jay Greguske wrote:
> > > > > On 12/10/2012 12:07 PM, Shahar Havivi wrote:
> > > > >> On 10.12.12 12:03, Perry Myers wrote:
> > > > >>> On 12/10/2012 12:00 PM, Shahar Havivi wrote:
> > > > >>>> On 10.12.12 10:55, jvlcek wrote:
> > > > >>>>> Shahar,
> > > > >>>>>
> > > > >>>>> It's complaining about the ec2-user not
being there?
> > > > >>>>>
> > > > >>>>> Are you specifying the ec2-user in the
cloud-init.conf file or are you just
> > > > >>>>> using root?
> > > > >>>> No,
> > > > >>>> Where is this file suppose to be?
> > > > >>>
> > > > >>> That version of cloud-init should be released with the
RHEL 6.4 public
> > > > >>> beta last week.
> > > > >>>
> > > > >>> It could be that the file is not properly showing up on
the beta
> > > > >>> channel. If you have access to the 6.4 Beta channels,
there's the core
> > > > >>> channel, optional, supplementary and then there should
be a new RHEL
> > > > >>> Common channel where cloud-init lives.
> > > > >>>
> > > > >>> Can you see if you have access to this channel?
> > > > >>>
> > > > >>> (adding some add'l folks to help with details on how
to get access to
> > > > >>> that channel)
> > > > >>>
> > > > >>> Perry
> > > > >> Thank you,
> > > > >> I will try to get 6.4
> > > > >
> > > > > The 6.4 Beta AMIs do not have cloud-init in them. They were
targeted to,
> > > > > but that didn't happen for one reason or another. They
should get it in
> > > > > a future snapshot, and certainly before the RC.
> > > >
> > > > Ah ok. Thanks for clarifying. What about availability to just grab
the
> > > > cloud-init package from the 6.4 beta channel? Should that work as
well?
> > > >
> > > > Shahar is working with oVirt and cloud-init, so grabbing from
RHN/CDN
> > > > would be sufficient. Doesn't need to be in an AMI
> > > >
> > > > Perry
> > >
> > > The beta channels with cloud-init should be available through RHN
> > > tomorrow or Monday.
> > >
> > > Cheers
> > > -- Dennis
> What is the channel name that include the cloud-init (I couldn't fine a
> channel with cloud-init in its name).
Found it in the common channel,
I have a problem installing it because I get glibc-common dependency
mismatch...
Is there other channel that I need my host to be register to?
You probably need the
Red Hat Enterprise Linux Server Beta channel as
well.
Cheers
-- Dennis
> >
> > The channels should be available now.
> >
> > -- Dennis
> >
9:06 a.m.
On 16.12.12 17:04, Dennis Gregorovic wrote:
On Sun, 2012-12-16 at 15:33 +0200, Shahar Havivi wrote:
> On 16.12.12 15:15, Shahar Havivi wrote:
> > On 14.12.12 21:22, Dennis Gregorovic wrote:
> > > On Thu, 2012-12-13 at 16:29 -0500, Dennis Gregorovic wrote:
> > > > On Mon, 2012-12-10 at 13:43 -0500, Perry Myers wrote:
> > > > > On 12/10/2012 01:41 PM, Jay Greguske wrote:
> > > > > > On 12/10/2012 12:07 PM, Shahar Havivi wrote:
> > > > > >> On 10.12.12 12:03, Perry Myers wrote:
> > > > > >>> On 12/10/2012 12:00 PM, Shahar Havivi wrote:
> > > > > >>>> On 10.12.12 10:55, jvlcek wrote:
> > > > > >>>>> Shahar,
> > > > > >>>>>
> > > > > >>>>> It's complaining about the ec2-user not
being there?
> > > > > >>>>>
> > > > > >>>>> Are you specifying the ec2-user in the
cloud-init.conf file or are you just
> > > > > >>>>> using root?
> > > > > >>>> No,
> > > > > >>>> Where is this file suppose to be?
> > > > > >>>
> > > > > >>> That version of cloud-init should be released with
the RHEL 6.4 public
> > > > > >>> beta last week.
> > > > > >>>
> > > > > >>> It could be that the file is not properly showing
up on the beta
> > > > > >>> channel. If you have access to the 6.4 Beta
channels, there's the core
> > > > > >>> channel, optional, supplementary and then there
should be a new RHEL
> > > > > >>> Common channel where cloud-init lives.
> > > > > >>>
> > > > > >>> Can you see if you have access to this channel?
> > > > > >>>
> > > > > >>> (adding some add'l folks to help with details
on how to get access to
> > > > > >>> that channel)
> > > > > >>>
> > > > > >>> Perry
> > > > > >> Thank you,
> > > > > >> I will try to get 6.4
> > > > > >
> > > > > > The 6.4 Beta AMIs do not have cloud-init in them. They were
targeted to,
> > > > > > but that didn't happen for one reason or another. They
should get it in
> > > > > > a future snapshot, and certainly before the RC.
> > > > >
> > > > > Ah ok. Thanks for clarifying. What about availability to just
grab the
> > > > > cloud-init package from the 6.4 beta channel? Should that work
as well?
> > > > >
> > > > > Shahar is working with oVirt and cloud-init, so grabbing from
RHN/CDN
> > > > > would be sufficient. Doesn't need to be in an AMI
> > > > >
> > > > > Perry
> > > >
> > > > The beta channels with cloud-init should be available through RHN
> > > > tomorrow or Monday.
> > > >
> > > > Cheers
> > > > -- Dennis
> > What is the channel name that include the cloud-init (I couldn't fine a
> > channel with cloud-init in its name).
> Found it in the common channel,
> I have a problem installing it because I get glibc-common dependency
> mismatch...
> Is there other channel that I need my host to be register to?
You probably need the Red Hat Enterprise Linux Server Beta channel as
well.
Cheers
-- Dennis
Thanks Dennis!
I manage to install the cloud-init in Rhel 6.4
The hostname can be set via nocloud CDROM but not the ip or the mac address.
also cloud init try for 5 minutes to call for this address:
url_helper.py[WARNING]: Calling
'http://169.254.169.254/2009-04-04/meta-data/instance-id' failed [0/120s]: http
error [404]
which for my understanding it shouldn't because I try to config it via the
drive (CDROM in this case).
When I try to set it via openstack, I use the "config-2" label in the CDROM
and set json file at this path:
openstack/latest/meta-data.json
at the log I am getting the line:
[CLOUDINIT] DataSourceAltCloud.py[DEBUG]: cloud_type: UNKNOWN
which indicate that its not recognize the the type (openstack).
Am I doing something wrong?
>
> > >
> > > The channels should be available now.
> > >
> > > -- Dennis
> > >
9:59 a.m.
On 12/17/2012 10:06 AM, Shahar Havivi wrote:
On 16.12.12 17:04, Dennis Gregorovic wrote:
> On Sun, 2012-12-16 at 15:33 +0200, Shahar Havivi wrote:
>> On 16.12.12 15:15, Shahar Havivi wrote:
>>> On 14.12.12 21:22, Dennis Gregorovic wrote:
>>>> On Thu, 2012-12-13 at 16:29 -0500, Dennis Gregorovic wrote:
>>>>> On Mon, 2012-12-10 at 13:43 -0500, Perry Myers wrote:
>>>>>> On 12/10/2012 01:41 PM, Jay Greguske wrote:
>>>>>>> On 12/10/2012 12:07 PM, Shahar Havivi wrote:
>>>>>>>> On 10.12.12 12:03, Perry Myers wrote:
>>>>>>>>> On 12/10/2012 12:00 PM, Shahar Havivi wrote:
>>>>>>>>>> On 10.12.12 10:55, jvlcek wrote:
>>>>>>>>>>> Shahar,
>>>>>>>>>>>
>>>>>>>>>>> It's complaining about the ec2-user not
being there?
>>>>>>>>>>>
>>>>>>>>>>> Are you specifying the ec2-user in the
cloud-init.conf file or are you just
>>>>>>>>>>> using root?
>>>>>>>>>> No,
>>>>>>>>>> Where is this file suppose to be?
>>>>>>>>> That version of cloud-init should be released with
the RHEL 6.4 public
>>>>>>>>> beta last week.
>>>>>>>>>
>>>>>>>>> It could be that the file is not properly showing up
on the beta
>>>>>>>>> channel. If you have access to the 6.4 Beta
channels, there's the core
>>>>>>>>> channel, optional, supplementary and then there
should be a new RHEL
>>>>>>>>> Common channel where cloud-init lives.
>>>>>>>>>
>>>>>>>>> Can you see if you have access to this channel?
>>>>>>>>>
>>>>>>>>> (adding some add'l folks to help with details on
how to get access to
>>>>>>>>> that channel)
>>>>>>>>>
>>>>>>>>> Perry
>>>>>>>> Thank you,
>>>>>>>> I will try to get 6.4
>>>>>>> The 6.4 Beta AMIs do not have cloud-init in them. They were
targeted to,
>>>>>>> but that didn't happen for one reason or another. They
should get it in
>>>>>>> a future snapshot, and certainly before the RC.
>>>>>> Ah ok. Thanks for clarifying. What about availability to just
grab the
>>>>>> cloud-init package from the 6.4 beta channel? Should that work
as well?
>>>>>>
>>>>>> Shahar is working with oVirt and cloud-init, so grabbing from
RHN/CDN
>>>>>> would be sufficient. Doesn't need to be in an AMI
>>>>>>
>>>>>> Perry
>>>>> The beta channels with cloud-init should be available through RHN
>>>>> tomorrow or Monday.
>>>>>
>>>>> Cheers
>>>>> -- Dennis
>>> What is the channel name that include the cloud-init (I couldn't fine a
>>> channel with cloud-init in its name).
>> Found it in the common channel,
>> I have a problem installing it because I get glibc-common dependency
>> mismatch...
>> Is there other channel that I need my host to be register to?
> You probably need the Red Hat Enterprise Linux Server Beta channel as
> well.
>
> Cheers
> -- Dennis
Thanks Dennis!
I manage to install the cloud-init in Rhel 6.4
The hostname can be set via nocloud CDROM but not the ip or the mac address.
also cloud init try for 5 minutes to call for this address:
url_helper.py[WARNING]: Calling
'http://169.254.169.254/2009-04-04/meta-data/instance-id' failed [0/120s]: http
error [404]
which for my understanding it shouldn't because I try to config it via the
drive (CDROM in this case).
When I try to set it via openstack, I use the "config-2" label in the CDROM
and set json file at this path:
openstack/latest/meta-data.json
at the log I am getting the line:
[CLOUDINIT] DataSourceAltCloud.py[DEBUG]: cloud_type: UNKNOWN
which indicate that its not recognize the the type (openstack).
Am I doing something wrong?
The data source: "DataSourceAltCloud" can only be used to pass in
"user-data" and it only
supports cloud types: EC2, RHEVm and vSphere.
What cloud back-end are you running on?
I thought you stated you are using the data source: "nocloud".
cloud-init functionality can be configured a bit using it's
configuration file. You might want
to experiment to make sure all the functionality you want is enabled in it.
For reference, the upstream version can be viewed here:
http://bazaar.launchpad.net/~cloud-init-dev/cloud-init/trunk/view/head:/c...
The warning from url_helper.py seems to indicate the ec2 style
meta-data is not
available. I'm not sure why. You might want to post a description of
your set-up
and ask about this warning upstream at: cloud-init(a)lists.launchpad.net
Joe
>>>> The channels should be available now.
>>>>
>>>> -- Dennis
>>>>
>
10:20 a.m.
On 17.12.12 10:59, jvlcek wrote:
On 12/17/2012 10:06 AM, Shahar Havivi wrote:
> On 16.12.12 17:04, Dennis Gregorovic wrote:
>> On Sun, 2012-12-16 at 15:33 +0200, Shahar Havivi wrote:
>>> On 16.12.12 15:15, Shahar Havivi wrote:
>>>> On 14.12.12 21:22, Dennis Gregorovic wrote:
>>>>> On Thu, 2012-12-13 at 16:29 -0500, Dennis Gregorovic wrote:
>>>>>> On Mon, 2012-12-10 at 13:43 -0500, Perry Myers wrote:
>>>>>>> On 12/10/2012 01:41 PM, Jay Greguske wrote:
>>>>>>>> On 12/10/2012 12:07 PM, Shahar Havivi wrote:
>>>>>>>>> On 10.12.12 12:03, Perry Myers wrote:
>>>>>>>>>> On 12/10/2012 12:00 PM, Shahar Havivi wrote:
>>>>>>>>>>> On 10.12.12 10:55, jvlcek wrote:
>>>>>>>>>>>> Shahar,
>>>>>>>>>>>>
>>>>>>>>>>>> It's complaining about the ec2-user
not being there?
>>>>>>>>>>>>
>>>>>>>>>>>> Are you specifying the ec2-user in the
cloud-init.conf file or are you just
>>>>>>>>>>>> using root?
>>>>>>>>>>> No,
>>>>>>>>>>> Where is this file suppose to be?
>>>>>>>>>> That version of cloud-init should be released
with the RHEL 6.4 public
>>>>>>>>>> beta last week.
>>>>>>>>>>
>>>>>>>>>> It could be that the file is not properly
showing up on the beta
>>>>>>>>>> channel. If you have access to the 6.4 Beta
channels, there's the core
>>>>>>>>>> channel, optional, supplementary and then there
should be a new RHEL
>>>>>>>>>> Common channel where cloud-init lives.
>>>>>>>>>>
>>>>>>>>>> Can you see if you have access to this channel?
>>>>>>>>>>
>>>>>>>>>> (adding some add'l folks to help with
details on how to get access to
>>>>>>>>>> that channel)
>>>>>>>>>>
>>>>>>>>>> Perry
>>>>>>>>> Thank you,
>>>>>>>>> I will try to get 6.4
>>>>>>>> The 6.4 Beta AMIs do not have cloud-init in them. They
were targeted to,
>>>>>>>> but that didn't happen for one reason or another.
They should get it in
>>>>>>>> a future snapshot, and certainly before the RC.
>>>>>>> Ah ok. Thanks for clarifying. What about availability to
just grab the
>>>>>>> cloud-init package from the 6.4 beta channel? Should that
work as well?
>>>>>>>
>>>>>>> Shahar is working with oVirt and cloud-init, so grabbing
from RHN/CDN
>>>>>>> would be sufficient. Doesn't need to be in an AMI
>>>>>>>
>>>>>>> Perry
>>>>>> The beta channels with cloud-init should be available through
RHN
>>>>>> tomorrow or Monday.
>>>>>>
>>>>>> Cheers
>>>>>> -- Dennis
>>>> What is the channel name that include the cloud-init (I couldn't
fine a
>>>> channel with cloud-init in its name).
>>> Found it in the common channel,
>>> I have a problem installing it because I get glibc-common dependency
>>> mismatch...
>>> Is there other channel that I need my host to be register to?
>> You probably need the Red Hat Enterprise Linux Server Beta channel as
>> well.
>>
>> Cheers
>> -- Dennis
> Thanks Dennis!
> I manage to install the cloud-init in Rhel 6.4
> The hostname can be set via nocloud CDROM but not the ip or the mac address.
> also cloud init try for 5 minutes to call for this address:
> url_helper.py[WARNING]: Calling
'http://169.254.169.254/2009-04-04/meta-data/instance-id' failed [0/120s]: http
error [404]
> which for my understanding it shouldn't because I try to config it via the
> drive (CDROM in this case).
>
> When I try to set it via openstack, I use the "config-2" label in the
CDROM
> and set json file at this path:
> openstack/latest/meta-data.json
>
> at the log I am getting the line:
> [CLOUDINIT] DataSourceAltCloud.py[DEBUG]: cloud_type: UNKNOWN
> which indicate that its not recognize the the type (openstack).
>
> Am I doing something wrong?
The data source: "DataSourceAltCloud" can only be used to pass in
"user-data" and it only
supports cloud types: EC2, RHEVm and vSphere.
What cloud back-end are you running on?
I am running on RHEV-M (oVirt)
I thought you stated you are using the data source:
"nocloud".
I am trying to run with nocloud and openstack
cloud-init functionality can be configured a bit using it's
configuration file. You might want
to experiment to make sure all the functionality you want is enabled in it.
For reference, the upstream version can be viewed here:
http://bazaar.launchpad.net/~cloud-init-dev/cloud-init/trunk/view/head:/c...
Thanks,
I will look at it
The warning from url_helper.py seems to indicate the ec2 style
meta-data is not
available. I'm not sure why. You might want to post a description of
your set-up
and ask about this warning upstream at: cloud-init(a)lists.launchpad.net
Joe
>>>>> The channels should be available now.
>>>>>
>>>>> -- Dennis
>>>>>
>>
4146
days inactive
4154
days old
21 comments
5 participants
participants (5)
-
Dennis Gregorovic -
Jay Greguske -
Joseph VLcek -
Perry Myers -
Shahar Havivi