Sorry Rich, I posted the my previous email inadvertently only to
you.
The answer to my own question regarding vxlan support for Juno is:
Yes, it works like a charm, what I was missing was the proper network
configuration for ovs and the br-ex interface on CentOS 7 and some
additional steps by creating the networks after deployment and the
right settings in the answer-file
I'll write a step by step how to for ML2 VXLAN OpenStack Juno
deployment with Packstack and post the link on this list in few hours.
Thanks!
- Arash
Our internal testing shows this should work for you, however our public
facing 2 node ml2-vxlan is failing to launch instances so there may be
some configuration error there.
On Sat, Oct 4, 2014 at 8:41 PM, Arash Kaffamanesh <ak(a)cloudssky.com>
wrote:
Hi Rich,
hello together,
Many thanks to you and all of you for your effort testing the
Juno release.
I'm trying to get a 2 node RDO Juno installation working with
Packstack (1 controller and 1 compute, each with 2 nics on
CentOS 7) and it seems that the vxlan is the default
networking mode now. But after the initial installation and
creating a tenant, user and networks (internal and external)
and spawning instances, the instances show up in the console
properly, and I can associate floating IPs to the instances,
but I can't ping or ssh into them.
On CentOS 7, the reason for me seems to be openvswitch related
and if I try to create the ifcfg-br-ex bridge by hand and plug
the external interface vis ovs into it, then I'm not able to
login to the controller host.
So my question is, does vxlan work on Juno at this time at
all :-)
And if yes, could someone provide any hint about how to create
the br-ex and create the interfaces properly on CentOS 7 for
this 2 node installation?
Thanks!
Arash
On Fri, Oct 3, 2014 at 3:56 PM, Rich Bowen <rbowen(a)redhat.com>
wrote:
The raw IRC transcripts from the RDO test day are
available at
http://meetbot.fedoraproject.org/rdo/2014-09-30/
Of particular interest, probably are the links that
are enumerated in
http://meetbot.fedoraproject.org/rdo/2014-09-30/rdo.2014-09-30-20.59.html
which show many of the bugs that were encountered or opened during the course of testing.
There's also some listed on
https://openstack.redhat.com/RDO_test_day_Juno_milestone_3_test_cases
Thank you all so much for participating in testing,
and helping find these things. Thanks also for the
people that answered questions all day long on IRC and
on this mailing list. You're making OpenStack better.
If you participated in testing, and haven't shared
your notes or results, please take a moment today to
do that, while the memory is fresh. You can write
these up anywhere - please link to them from the Test
Cases, and please open tickets if you encountered
problems. It's always better to open a ticket, if
you're not sure if the issue has been raised before.
Start here:
https://bugzilla.redhat.com/enter_bug.cgi?product=RDO
Finally, a reminder that, although test day is over,
you're always encouraged to test the latest builds,
and report your findings here - on this list - and on
IRC, so that together we can continue to make
OpenStack better.
* Test day details -
https://openstack.redhat.com/RDO_test_day_Juno_milestone_3
* Tests and results -
https://openstack.redhat.com/RDO_test_day_Juno_milestone_3_test_cases
_______________________________________________
Rdo-list mailing list
Rdo-list(a)redhat.com
https://www.redhat.com/mailman/listinfo/rdo-list