For me mail is ok, but it could work on any other format.
The precious thing is a summary of what happen in the OpenStack world during
the last week with the TL;DR format. Thanks for that ;)
Le 18 janv. 2016 à 16:12, Allison Price
On 10:16 Jan 19, Jean-Daniel Bonnetot wrote:
> For me mail is ok, but it could work on any other format.
> The precious thing is a summary of what happen in the OpenStack world during
> the last week with the TL;DR format. Thanks for that ;)
Do you mean the Dev Digest? It was originally in the
The physical router is not getting a arp reply for the vm from neutron
router when snat is disabled. When floating ip is used, the router creates
one more interface on its qg- interface for that floating ip associated
with the vm and when arp request is broadcasted, the neutron router
You won't get an ARP reply at your physical router unless it's on the same
network as your VM, which it isn't if it's behind a neutron router.
It sounds like you still need to add a route on your physical router to
push all tenant network traffic down to the external interface of your
I'm seeing the following error in Fuel 6.1:
Deployment has failed. Method granular_deploy. Failed to execute hook
> 'puppet' Puppet run failed. Check puppet logs for details
> priority: 200
> fail_on_error: true
> type: puppet
> - '1'
On 01/19/2016 02:28 PM, Mike Perez wrote:
> Do you mean the Dev Digest? It was originally in the newsletter, and then
> people at the summit approached me about making it more visible, so it's now
> a separate thing and emailed to the dev and operators list weekly.
Join us tomorrow for our weekly meeting, January 14th at 17:00UTC in
The agenda can be found here, and please add to it if you want to get
something on the agenda:
This week we hope to have someone working on TOSCA join
To expand on Joseph's explanation: when SNAT is enabled, an IP is pulled from
the floating pool and assigned as a "default SNAT" for the router when its
gateway is set. Similar to how your home router has a single external IP and
all your internal devices SNAT out from that IP, all Vms on that
Aaron Segura wrote on 01/16/2016 12:19:53 PM:
> You shouldn't have to do anything other than disable SNAT and set a
> route for your tenant network upstream.
Indeed, I have exercised exactly this.
I am trying to stick to the new openstack client CLI, but sometimes I
get completely lost.
So I used to do with python-novaclient instance snapshots like this:
nova image-create snapshotname
I just cannot understand how to do the same with the new client. Could
I believe the correct command is:
openstack server image create
You can use `openstack help server image create` to check the usage.
`openstack help` will print all available commands.
On 01/19/2016 10:27 AM, Saverio Proto wrote:
> Hello there,
> I am trying to
Thanks for your inputs.
But I am still confused as Aaron and Mike are suggesting that it is
possible and Joseph and Kevin are suggesting its not possible.
I tried to ping from the vm in openstack to outside of the cloud with only
fixed ip assigned, but ping failed. When
It's possible. We do it all the time.
However, without proper routing, Kevin and Joseph are correct. The VM will
never receive replies to outbound packets because the upstream devices
don't know where to send them.
I also forgot to mention - The edge device also needs to NAT the fixed IP
Mail list logo