Open Stack

Hi thanks!

Yeah I got a working image and all, I just don't see the routing tables in
the log after start up.. Some other images seem to do that though. I do get
the keys and everything onto the host so that's all good. Just would like
that same output so I can see / verify what it's doing.

Alex
 On 10 Jun 2014 17:53, "Abel Lopez" <alopgeek at gmail.com> wrote:

> Distros, not distress. DYAC
>
> On Jun 10, 2014, at 9:52 AM, Abel Lopez <alopgeek at gmail.com> wrote:
>
> > It’s really neat and quite easy.
> > Most distress have a cloud-init package available for install. If you’re
> making your own images, just make sure to include that in the build.
> > Also, make sure whatever run-level manager you’re using is set to start
> cloud-init at boot (upstart/chkconfig/etc)
> > For RH based builds, you may need to include EPEL, for Fedora it’s part
> of the yum repo, for Ubuntu, it’s included in the apt repo.
> >
> > On Jun 10, 2014, at 9:44 AM, Alex Leonhardt <aleonhardt.py at gmail.com>
> wrote:
> >
> >> Hi guys,
> >>
> >> Am new to OpenStack and Cloud-Init. I've seen that with some images one
> gets to see some ci-info with the routing table printed, how can I do that
> with a home baked image ? Any clues or pointers would be appreciated!
> >>
> >> Alex
> >>
> >> _______________________________________________
> >> OpenStack-operators mailing list
> >> OpenStack-operators at lists.openstack.org
> >> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators
> >
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-operators/attachments/20140610/a2664cbc/attachment.html>