Open Stack

Sadly we already read that blog, and didnt work either :(

I really cant believe that all the people that has an already running
environment didnt deal with this , or maybe they bundeled they own image and
theyre not using cloud-init

Regards
Lele

2011/5/30 Diego Parrilla Santamaría <diego.parrilla.santamaria at gmail.com>

> Hi Leandro,
>
> We have an open issue in our distro regarding this topic. There is a
> workaround in this blog
> http://hugokuo-hugo.blogspot.com/2011/05/prerouting-169254169254-should-not-be.html
>
> Sadly, it did not work for us, or we did something wrong...
>
> Let us know if it works for you,
>
> Regards
> Diego
>
> --
>  Diego Parrilla
> <http://www.stackops.com>*CEO*
> *www.stackops.com | * diego.parrilla at stackops.com** | +34 649 94 43 29 |
> skype:diegoparrilla*
> * <http://www.stackops.com>
> *
>
> *
>
> ******************** ADVERTENCIA LEGAL ********************
> Le informamos, como destinatario de este mensaje, que el correo electrónico
> y las comunicaciones por medio de Internet no permiten asegurar ni
> garantizar la confidencialidad de los mensajes transmitidos, así como
> tampoco su integridad o su correcta recepción, por lo que STACKOPS
> TECHNOLOGIES S.L. no asume responsabilidad alguna por tales circunstancias.
> Si no consintiese en la utilización del correo electrónico o de las
> comunicaciones vía Internet le rogamos nos lo comunique y ponga en nuestro
> conocimiento de manera inmediata. Este mensaje va dirigido, de manera
> exclusiva, a su destinatario y contiene información confidencial y sujeta al
> secreto profesional, cuya divulgación no está permitida por la ley. En caso
> de haber recibido este mensaje por error, le rogamos que, de forma
> inmediata, nos lo comunique mediante correo electrónico remitido a nuestra
> atención y proceda a su eliminación, así como a la de cualquier documento
> adjunto al mismo. Asimismo, le comunicamos que la distribución, copia o
> utilización de este mensaje, o de cualquier documento adjunto al mismo,
> cualquiera que fuera su finalidad, están prohibidas por la ley.
>
> ***************** PRIVILEGED AND CONFIDENTIAL ****************
> We hereby inform you, as addressee of this message, that e-mail and
> Internet do not guarantee the confidentiality, nor the completeness or
> proper reception of the messages sent and, thus, STACKOPS TECHNOLOGIES S.L.
> does not assume any liability for those circumstances. Should you not agree
> to the use of e-mail or to communications via Internet, you are kindly
> requested to notify us immediately. This message is intended exclusively for
> the person to whom it is addressed and contains privileged and confidential
> information protected from disclosure by law. If you are not the addressee
> indicated in this message, you should immediately delete it and any
> attachments and notify the sender by reply e-mail. In such case, you are
> hereby notified that any dissemination, distribution, copying or use of this
> message or any attachments, for any purpose, is strictly prohibited by law.
>
>
>
>
> On Fri, May 27, 2011 at 10:01 PM, Leandro Reox <leandro.reox at gmail.com>wrote:
>
>> Hi all,
>>
>> In a multinode environment has anyone succeed booting up images ( ubuntu -
>> cloud init ) that request the metadata to the ip 169.254.269.254 ?
>>
>> NOTE: instances booting on the controller node (that has also compute
>> services running, boots up ok ... no luck getting instances running on the
>> ADDITIONAL compute node :( )
>>
>> - Already tried
>> -- iptables rule on the controller/network node
>> -- ip addres on the loopback  controller/network node
>> -- ip address on the br100 controller/network node
>> -- static route on the aditional compute node
>> -- iptables rule on  the aditional compute node
>> -- ip address on the loopback  on the aditional compute node
>> -- ip address on the br100 on the aditional compute node
>>
>> Still the same ugly message !
>>
>> tcpdumping all over the network , the request is sent back from the
>> network node repliing with the 169.254.269.254  but doesnt getting into the
>> VM ?
>>
>> Any clues of how to get this working ????
>>
>>
>> Best Regards
>>
>> lele
>>
>> _______________________________________________
>> 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/20110530/97144073/attachment-0002.html>