Problem spinning up instance in
by Scott Kaplan
I'm having trouble spinning up the ami-69e0bc2c in us-west-1a. I don't have any trouble in us-east-1d
I'm launching the instance, but it never answers pings. Here is what I see in the system log:
>
> [ 15.400782] acpid[372]: cannot open input layer
> [ 15.401526] acpid[372]: RTNETLINK1 answers: No such file or directory
> [ 15.410649] acpid[372]: acpid: error talking to the kernel via netlink
> [ 15.427546] acpid[382]: starting up with netlink and the input layer
> Started Command Scheduler.
> [ 18.062711] nf_conntrack version 0.5.0 (4732 buckets, 18928 max)
> [ 18.065207] ip6_tables: (C) 2000-2006 Netfilter Core Team
>
> [r
> [H
> [J
>
> Fedora release 16 (Verne)
> Kernel 3.1.0-7.fc16.x86_64 on an x86_64 (hvc0)
>
> localhost login: Bringing up loopback interface: [ OK ]
>
> Bringing up interface eth0:
> Determining IP information for eth0.../etc/init.d/functions: line 58: /dev/stderr: Permission denied
> /etc/rc.d/init.d/functions: line 58: /dev/stderr: Permission denied
> /etc/init.d/functions: line 58: /dev/stderr: Permission denied
> /etc/rc.d/init.d/functions: line 58: /dev/stderr: Permission denied
> done.
> [ OK ]
12 years, 2 months
OpenNebula approved
by Jaime Melis
Dear All,
We're a few weeks away from F17 features submission deadline and we've been
working hard (especially Shaw Starr - CC) in submitting OpenNebula package
dependencies. OpenNebula would even work without those not yet complete
dependencies since they're mostly ruby gems which speed up OpenNebula
(although we're confident they will all be there for the submission
deadline), so we would like to move on to the next stage and start
submitting OpenNebula for feature review to get it approved.
Could anyone help us out with the process we must follow to get OpenNebula
to be an accepted feature?
Regards,
Jaime
--
Jaime Melis
Project Engineer
OpenNebula - The Open Source Toolkit for Cloud Computing
www.OpenNebula.org | jmelis(a)opennebula.org
12 years, 2 months